From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
Ricard Wanderlof <ricard.wanderlof@axis.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2 1/1] ASoC: core: Do not print an actual error when deferring probe
Date: Wed, 18 May 2016 17:53:49 +0200 [thread overview]
Message-ID: <2174266.52DIgyL9R9@ws-stein> (raw)
In-Reply-To: <20160518152028.GM8104@sirena.org.uk>
On Wednesday 18 May 2016 16:20:28, Mark Brown wrote:
> On Wed, May 18, 2016 at 05:07:00PM +0200, Alexander Stein wrote:
> > In case there is no DAI (yet), do not print an error, this might happen
> > a lot of times. Print a notice instead.
>
> Oh, and the other thing about this which I should have mentioned is that
> it applies to every single resource acquisition in the kernel - this
> needs addressing at a global error rather than piecemeal. Raphael was
> intending to work on avoiding probe deferral in the first place by
> sorting probe and there were also some proposals to have a helper for
> printing error messages which would suppress the display of probe
> deferral errors before the final run at late initcall. Obviously the
> second mechanism is substantially simpler to implement.
I remember those patches a bit. But working with late initcall sound to me
this has no effect on probe deferral in drivers loaded by modules, no?
Regards,
Alexander
next prev parent reply other threads:[~2016-05-18 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 15:07 [PATCH v2 1/1] ASoC: core: Do not print an actual error when deferring probe Alexander Stein
2016-05-18 15:10 ` Ricard Wanderlof
2016-05-18 15:20 ` Mark Brown
2016-05-18 15:53 ` Alexander Stein [this message]
2016-05-18 16:08 ` Mark Brown
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=2174266.52DIgyL9R9@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=ricard.wanderlof@axis.com \
--cc=tiwai@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.