All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] sound: soc-core: make kernel complaints on -EPROBE_DEFER dev_dbg
Date: Sat, 12 Nov 2016 10:00:14 +0000	[thread overview]
Message-ID: <20161112100014.cwbwkls3kgphj5bz@sirena.org.uk> (raw)
In-Reply-To: <20161109163658.GA21606@localhost.localdomain>


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

On Wed, Nov 09, 2016 at 05:36:58PM +0100, Ladislav Michl wrote:
> On Wed, Nov 09, 2016 at 03:22:09PM +0000, Mark Brown wrote:

> > How do we know that it's not a kernel misconfiguration?  It's common for
> > people to not build some of the component drivers they need.

> Is what you described really a misconfiguration? Enabling debug when
> something does not work seems obvious thing to do, but okay, perhaps
> anything bellow error level would make me happy enough.

Yes, it's something that's really common when people configure their own
kernels.

> > > > If you don't like deferred probing please contribute to the efforts
> > > > to order probing.

> As a side note, which efforts are you reffering to here?

Things like Raphael's device dependencies work.

> > > I just tried to make it consistend to other subsystems where patches to
> > > silence deferred probing warnings are accepted...

> > Which subsystems are these?  We should look at fixing them...

> tty and usb for example. I do not consider wise to looking at them until
> this very subsystem gets fixed first to not distract ourselves ;-)
> (Also I have admit, that accepted patches hide error message on deferred
> probe only, but above occurs _also_ on deferred probe and yes, it would be
> nice to have that fixed)

This really does make it harder to figure out what's going on when the
dependency is actually missing - it transforms things into a silent
failure.

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

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



      reply	other threads:[~2016-11-12 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 14:00 [PATCH] sound: soc-core: make kernel complaints on -EPROBE_DEFER dev_dbg Ladislav Michl
2016-11-09 14:36 ` Mark Brown
2016-11-09 15:14   ` Ladislav Michl
2016-11-09 15:22     ` Mark Brown
2016-11-09 16:36       ` Ladislav Michl
2016-11-12 10:00         ` 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=20161112100014.cwbwkls3kgphj5bz@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ladis@linux-mips.org \
    --cc=lgirdwood@gmail.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.