From: "Danilo Krummrich" <dakr@kernel.org>
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Cc: "Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <david@davidgow.net>,
"Rae Moar" <raemoar63@gmail.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Daniel Scally" <djrscally@gmail.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<kunit-dev@googlegroups.com>, <linux-acpi@vger.kernel.org>,
<driver-core@lists.linux.dev>, <linux-gpio@vger.kernel.org>
Subject: Re: (subset) [PATCH v4 0/5] software node: provide support for fw_devlink
Date: Wed, 15 Jul 2026 23:30:26 +0200 [thread overview]
Message-ID: <DJZGR6NV2WK5.2ZRW7VZIRO3LD@kernel.org> (raw)
In-Reply-To: <20260715212830.3077100-1-dakr@kernel.org>
On Wed Jul 15, 2026 at 11:28 PM CEST, Danilo Krummrich wrote:
> On Mon, 13 Jul 2026 13:14:43 +0200, Bartosz Golaszewski wrote:
>> [PATCH v4 0/5] software node: provide support for fw_devlink
>
> Applied, thanks!
>
> Branch: topic/swnode
> Tree: git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
>
> [1/5] kunit: provide a set of fwnode-oriented helpers
> commit: 9fdbdb528488
> [2/5] software node: add fw_devlink support
> commit: 37e586675993
> [3/5] software node: add kunit tests for fw_devlink support
> commit: eecba5978729
> [4/5] MAINTAINERS: add myself as reviewer of software node support
> commit: 122630406245
>
> The patches are in the topic/swnode topic branch and will be merged into the
> corresponding target branch soon.
I will provide a signed tag once I have the 0-day result.
Thanks,
Danilo
prev parent reply other threads:[~2026-07-15 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:14 [PATCH v4 0/5] software node: provide support for fw_devlink Bartosz Golaszewski
2026-07-13 11:14 ` [PATCH v4 1/5] kunit: provide a set of fwnode-oriented helpers Bartosz Golaszewski
2026-07-13 11:14 ` [PATCH v4 2/5] software node: add fw_devlink support Bartosz Golaszewski
2026-07-13 11:14 ` [PATCH v4 3/5] software node: add kunit tests for " Bartosz Golaszewski
2026-07-13 11:14 ` [PATCH v4 4/5] MAINTAINERS: add myself as reviewer of software node support Bartosz Golaszewski
2026-07-13 11:14 ` [PATCH v4 5/5] gpio: kunit: add test cases verifying swnode devlink support Bartosz Golaszewski
2026-07-13 11:46 ` [PATCH v4 0/5] software node: provide support for fw_devlink Bartosz Golaszewski
2026-07-15 21:28 ` (subset) " Danilo Krummrich
2026-07-15 21:30 ` 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=DJZGR6NV2WK5.2ZRW7VZIRO3LD@kernel.org \
--to=dakr@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brendan.higgins@linux.dev \
--cc=brgl@kernel.org \
--cc=david@davidgow.net \
--cc=djrscally@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=raemoar63@gmail.com \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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