[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210723140039.GD5221@sirena.org.uk>
Date: Fri, 23 Jul 2021 15:00:39 +0100
From: Mark Brown <broonie@...nel.org>
To: "Limonciello, Mario" <Mario.Limonciello@....com>
Cc: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"Mukunda, Vijendar" <Vijendar.Mukunda@....com>,
"markpearson@...ovo.com" <markpearson@...ovo.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] ASoC: amd: Don't show messages about deferred
probing by default
On Fri, Jul 23, 2021 at 01:04:51PM +0000, Limonciello, Mario wrote:
> > On Thu, Jul 22, 2021 at 08:27:27AM -0500, Mario Limonciello wrote:
> > > This isn't useful to a user, especially as probing will run again.
> > > Use the dev_err_probe helper to hide the deferrerd probing messages.
> > The reason we have these error messages is that they are very useful to
> > users if they ever find that the device isn't instantiating due to some
> > missing dependency or something that leaves it stuck in probe deferral,
> > they give some hint as to what might be wrong.
> Right, but they should be at debugging level, if someone has a problem they
> turn on dynamic debugging for the module and then can see these messages.
Your commit message says that reporting the error isn't useful, I am
flagging that it is useful to have the messages be available to people.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists