All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	linux-kernel@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH RESEND v2 0/2] driver core: bus: Fix issues related to bus_rescan_devices_helper()
Date: Tue, 12 Nov 2024 12:48:11 +0100	[thread overview]
Message-ID: <2024111228-snowcap-counting-b833@gregkh> (raw)
In-Reply-To: <20241022-bus_match_unlikely-v2-0-1a6f8e6839a0@quicinc.com>

On Tue, Oct 22, 2024 at 07:18:00PM +0800, Zijun Hu wrote:
> This patch series is to fix issues related to bus_rescan_devices_helper().
> 
> The function is improperly used for 2 incompatible scenarios as
> explained below:
> 
> Scenario A: scan drivers for a single device user specify
>  - user may care about precise synchronous scanning result, so the
>    function can not collapse error codes.

I do not understand this, what is wrong that this is fixing?

> Scenario B: scan drivers for all devices of a bus
>  - user may need to scan drivers for a bus's devices as many as
>    possible, so the function needs to ignore inconsequential error
>    codes for a device in order to continue to scan for next device.

How often is that needed?  And why can't that still work with the
existing code?

thanks,

greg k-h

  parent reply	other threads:[~2024-11-12 11:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 11:18 [PATCH RESEND v2 0/2] driver core: bus: Fix issues related to bus_rescan_devices_helper() Zijun Hu
2024-10-22 11:18 ` [PATCH RESEND v2 1/2] driver core: bus: Fix drivers_probe_store() giving user wrong scanning result Zijun Hu
2024-10-22 11:18 ` [PATCH RESEND v2 2/2] driver core: bus: Correct API bus_rescan_devices() behavior Zijun Hu
2024-11-12 11:48 ` Greg Kroah-Hartman [this message]
2024-11-13 13:42   ` [PATCH RESEND v2 0/2] driver core: bus: Fix issues related to bus_rescan_devices_helper() Zijun Hu
2024-11-13 13:43   ` Zijun Hu

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=2024111228-snowcap-counting-b833@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_zijuhu@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=zijun_hu@icloud.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.