From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Feng Tang <feng.tang@intel.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] async: Add cmdline option to specify drivers to be async probed
Date: Wed, 30 Jan 2019 08:16:02 +0100 [thread overview]
Message-ID: <20190130071602.GB3657@kroah.com> (raw)
In-Reply-To: <1548830287-4281-1-git-send-email-feng.tang@intel.com>
On Wed, Jan 30, 2019 at 02:38:07PM +0800, Feng Tang wrote:
> Asynchronous driver probing can help much on kernel fastboot, and
> this option can provide a flexible way to optimize and quickly verify
> async driver probe.
>
> Also it will help in below cases:
> * Some driver actually covers several families of HWs, some of which
> could use async probing while others don't. So we can't simply
> turn on the PROBE_PREFER_ASYNCHRONOUS flag in driver, but use this
> cmdline option, like igb driver async patch discussed at
> https://www.spinics.net/lists/netdev/msg545986.html
>
> * For SOC (System on Chip) with multiple spi or i2c controllers, most
> of the slave spi/i2c devices will be assigned with fixed controller
> number, while async probing may make those controllers get different
> index for each boot, which prevents those controller drivers to be
> async probed. For platforms not using these spi/i2c slave devices,
> they can use this cmdline option to benefit from the async probing.
>
> Suggested-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> ---
> drivers/base/dd.c | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
This is v3 and yet no change information below the --- line saying what
is different from previous versions at all?
Not good, please fix.
greg k-h
next prev parent reply other threads:[~2019-01-30 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 6:38 Feng Tang
2019-01-30 7:16 ` Greg Kroah-Hartman [this message]
2019-01-30 7:23 Feng Tang
2019-01-30 16:27 ` Randy Dunlap
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=20190130071602.GB3657@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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
all inboxes | Powered by JetHome®