All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: [PATCH 1/1] ASoC: core: Do not print an actual error when deferring probe
Date: Thu, 19 May 2016 11:34:53 +0100	[thread overview]
Message-ID: <20160519103453.GC8206@sirena.org.uk> (raw)
In-Reply-To: <s5hinyazggk.wl-tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]

On Thu, May 19, 2016 at 08:53:31AM +0200, Takashi Iwai wrote:
> Alexander Stein wrote:
> > On Wednesday 18 May 2016 21:33:01, Takashi Iwai wrote:

> > > dev_notice() lowers the log level to somewhat between info and
> > > warning, and it looks like a sensible choice to me.

> > You want me to change the subject to be more clear?

> If the patch can go in, yes.  The changelog text should be also
> clearer why it's needed and what it gives, too.

There's also the problem with it just squashing all errors, not just
probe deferral.  I really would prefer to see at least some attempt to
push this into a central helper rather than just open coding hacks in
every single user though, that's the thing here.  We want a simple and
consistent way of handling this, going round and doing something custom
at every single caller is going to result in inconsistent behaviour and
means that it's harder to deploy and new and better solutions.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2016-05-19 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 13:41 [PATCH 1/1] ASoC: core: Do not print an actual error when deferring probe Alexander Stein
2016-05-18 14:25 ` Ricard Wanderlof
2016-05-18 15:08 ` Mark Brown
2016-05-18 15:18   ` Alexander Stein
2016-05-18 15:28     ` Mark Brown
2016-05-18 15:50       ` Alexander Stein
2016-05-18 16:21         ` Mark Brown
2016-05-18 16:57           ` Takashi Iwai
2016-05-18 17:20             ` Mark Brown
2016-05-18 19:33               ` Takashi Iwai
2016-05-19  6:28                 ` Alexander Stein
2016-05-19  6:53                   ` Takashi Iwai
2016-05-19 10:34                     ` Mark Brown [this message]

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=20160519103453.GC8206@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alexander.stein@systec-electronic.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /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.