From: Greg KH <gregkh@linuxfoundation.org>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Messaging verbosity backport
Date: Fri, 25 Feb 2022 13:33:42 +0100 [thread overview]
Message-ID: <YhjMpqwE6BDjzNj7@kroah.com> (raw)
In-Reply-To: <YhjK4RMbHjFc6xal@kroah.com>
On Fri, Feb 25, 2022 at 01:26:09PM +0100, Greg KH wrote:
> On Wed, Feb 23, 2022 at 11:06:47PM +0000, Limonciello, Mario wrote:
> > [Public]
> >
> > Hi,
> >
> > By default some laptops show this on every boot. It's not useful and was degraded to debug in a future kernel.
> >
> > [drm:dp_retrieve_lttpr_cap [amdgpu]] *ERROR* dp_retrieve_lttpr_cap: Read LTTPR caps data failed.
> >
> > Please backport
> >
> > commit 1d925758ba1a5d2716a847903e2fd04efcbd9862 ("drm/amd/display: Reduce dmesg error to a debug print") to decrease verbosity.
>
> Now queued up, thanks.
No, not at all, it breaks the build. Did you try this yourself?
dropped.
greg k-h
next prev parent reply other threads:[~2022-02-25 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 23:06 Messaging verbosity backport Limonciello, Mario
2022-02-25 12:26 ` Greg KH
2022-02-25 12:33 ` Greg KH [this message]
2022-02-25 13:04 ` Limonciello, Mario
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YhjMpqwE6BDjzNj7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Mario.Limonciello@amd.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox