From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] driver core: add a debugfs entry to show deferred devices
Date: Wed, 20 Jun 2018 11:54:15 +0100 [thread overview]
Message-ID: <20180620105415.GC6242@sirena.org.uk> (raw)
In-Reply-To: <20180619225145.GA23389@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
On Wed, Jun 20, 2018 at 07:51:45AM +0900, Greg Kroah-Hartman wrote:
> And what is the use of this file? What can you do with this
> information? Who is going to use it? Don't we have other deferred
> probe debugging somewhere else?
Pretty much all we have right now is kernel log messages, and people
keep trying to suppress those as they're quite noisy sometimes. Ideally
the device dependency stuff will reduce that problem but I'm not sure
how that's getting on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-06-20 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:59 [PATCH] driver core: add a debugfs entry to show deferred devices Javier Martinez Canillas
2018-06-19 21:06 ` Andy Shevchenko
2018-06-19 22:51 ` Greg Kroah-Hartman
2018-06-19 23:43 ` Andy Shevchenko
2018-06-20 9:04 ` Javier Martinez Canillas
2018-06-20 8:46 ` Javier Martinez Canillas
2018-06-20 9:48 ` Javier Martinez Canillas
2018-06-20 10:54 ` 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=20180620105415.GC6242@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tomeu.vizoso@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox