From: "Danilo Krummrich" <dakr@kernel.org>
To: "Runyu Xiao" <runyu.xiao@seu.edu.cn>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<driver-core@lists.linux.dev>, <linux@armlinux.org.uk>,
<andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<kys@microsoft.com>, <haiyangz@microsoft.com>,
<wei.liu@kernel.org>, <decui@microsoft.com>,
<longli@microsoft.com>, <nipun.gupta@amd.com>,
<nikhil.agarwal@amd.com>, <linux-remoteproc@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-hyperv@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jianhao.xu@seu.edu.cn>
Subject: Re: [PATCH v2 0/4] Convert remaining buses to generic driver_override handling
Date: Mon, 08 Jun 2026 20:09:40 +0200 [thread overview]
Message-ID: <DJ3VBAU543O4.1MCNNBJ7U9IRN@kernel.org> (raw)
In-Reply-To: <20260604035239.1711889-1-runyu.xiao@seu.edu.cn>
On Thu Jun 4, 2026 at 5:52 AM CEST, Runyu Xiao wrote:
> Runyu Xiao (4):
> amba: use generic driver_override infrastructure
> rpmsg: core: use generic driver_override infrastructure
> vmbus: use generic driver_override infrastructure
> cdx: use generic driver_override infrastructure
Given that you changed the approach to use the new driver_override
infrastructure, I assume you read the message in [1]?
In this message I also explained that this all has been addressed and was merged
into driver-core-next already.
[1] https://lore.kernel.org/all/DIYPR0K2CZW7.254R8K7ONBX5D@kernel.org/
prev parent reply other threads:[~2026-06-08 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 16:08 [PATCH] driver core: enforce device_lock for driver_match_device() Runyu Xiao
2026-06-02 16:39 ` Greg KH
2026-06-02 16:44 ` Danilo Krummrich
2026-06-03 3:36 ` Runyu Xiao
2026-06-04 3:52 ` [PATCH v2 0/4] Convert remaining buses to generic driver_override handling Runyu Xiao
2026-06-04 3:52 ` [PATCH v2 1/4] amba: use generic driver_override infrastructure Runyu Xiao
2026-06-04 3:52 ` [PATCH v2 2/4] rpmsg: core: " Runyu Xiao
2026-06-08 17:47 ` Mathieu Poirier
2026-06-04 3:52 ` [PATCH v2 3/4] vmbus: " Runyu Xiao
2026-06-04 4:13 ` sashiko-bot
2026-06-04 3:52 ` [PATCH v2 4/4] cdx: " Runyu Xiao
2026-06-04 4:08 ` sashiko-bot
2026-06-08 18:09 ` Danilo Krummrich [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=DJ3VBAU543O4.1MCNNBJ7U9IRN@kernel.org \
--to=dakr@kernel.org \
--cc=andersson@kernel.org \
--cc=decui@microsoft.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=kys@microsoft.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=longli@microsoft.com \
--cc=mathieu.poirier@linaro.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=rafael@kernel.org \
--cc=runyu.xiao@seu.edu.cn \
--cc=wei.liu@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 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.