From: "Jinhui Guo" <guojinhui.liam@bytedance.com>
To: <guojinhui.liam@bytedance.com>
Cc: <alexanderduyck@fb.com>, <bhelgaas@google.com>,
<bvanassche@acm.org>, <dakr@kernel.org>,
<dan.j.williams@intel.com>, <frederic@kernel.org>,
<gregkh@linuxfoundation.org>, <helgaas@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<rafael@kernel.org>, <tj@kernel.org>
Subject: Re: [PATCH v2 0/3] Add NUMA-node-aware synchronous probing to driver core
Date: Tue, 27 Jan 2026 10:32:00 +0800 [thread overview]
Message-ID: <20260127023200.414-1-guojinhui.liam@bytedance.com> (raw)
In-Reply-To: <20260126091749.307-1-guojinhui.liam@bytedance.com>
On Mon Jan 26, 2026 17:17:49 -0800, Jinhui Guo wrote:
> Hi Dan,
>
> Thank you for your time, and apologies for the delayed reply.
>
> I understand your concerns about stability and hope for better PCI regression
> handling. However, I believe introducing NUMA-node awareness to the driver
> core's asynchronous probe path is the better solution:
"asynchronous probe path" -> "synchronous probe path"
Apologies for the typo.
Best Regards,
Jinhui
next prev parent reply other threads:[~2026-01-27 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 14:52 Jinhui Guo
2026-01-22 14:52 ` [PATCH v2 1/3] driver core: Introduce helper function __device_attach_driver_scan() Jinhui Guo
2026-01-22 14:52 ` [PATCH v2 2/3] driver core: Add NUMA-node awareness to the synchronous probe path Jinhui Guo
2026-01-22 14:52 ` [PATCH v2 3/3] PCI: Clean up NUMA-node awareness in pci_bus_type probe Jinhui Guo
2026-01-24 1:04 ` [PATCH v2 0/3] Add NUMA-node-aware synchronous probing to driver core dan.j.williams
2026-01-26 9:17 ` Jinhui Guo
2026-01-27 2:32 ` Jinhui Guo [this message]
2026-01-27 3:37 ` dan.j.williams
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=20260127023200.414-1-guojinhui.liam@bytedance.com \
--to=guojinhui.liam@bytedance.com \
--cc=alexanderduyck@fb.com \
--cc=bhelgaas@google.com \
--cc=bvanassche@acm.org \
--cc=dakr@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tj@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®