From: Danilo Krummrich <dakr@kernel.org>
To: Russ Weight <russ.weight@linux.dev>
Cc: dakr@kernel.org, mcgrof@kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH v1 0/3] Remove Russ Weight from kernel development files
Date: Tue, 1 Sep 2026 18:42:48 +0200 [thread overview]
Message-ID: <20260901164248.1327630-1-dakr@kernel.org> (raw)
In-Reply-To: <20260818194648.1014604-1-russ.weight@linux.dev>
On Tue, 18 Aug 2026 13:46:45 -0600, Russ Weight wrote:
> [PATCH v1 0/3] Remove Russ Weight from kernel development files
Applied, thanks!
Branch: driver-core-linus
Tree: git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
[1/3] firmware_loader: Change contact for sysfs nodes
commit: 6db237eb5167
[ Since we have a driver-core mailing list, use it as contact
information instead of myself. - Danilo ]
[2/3] CREDITS: Add CREDITS entry for Firmware Upload
commit: 0d3e690c1129
[3/3] MAINTAINERS: Remove Russ Weight from Firmware Loader
commit: f6d752278c13
The patches will appear in the next linux-next integration (typically within 24
hours on weekdays).
The patches are queued up for Linus's tree and should land in the next -rc
release.
prev parent reply other threads:[~2026-09-01 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 19:46 [PATCH v1 0/3] Remove Russ Weight from kernel development files Russ Weight
2026-08-18 19:46 ` [PATCH v1 1/3] firmware_loader: Change contact for sysfs nodes Russ Weight
2026-08-18 19:46 ` [PATCH v1 2/3] CREDITS: Add CREDITS entry for Firmware Upload Russ Weight
2026-08-18 19:46 ` [PATCH v1 3/3] MAINTAINERS: Remove Russ Weight from Firmware Loader Russ Weight
2026-08-19 21:13 ` [PATCH v1 0/3] Remove Russ Weight from kernel development files Danilo Krummrich
2026-09-01 16:42 ` 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=20260901164248.1327630-1-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=russ.weight@linux.dev \
/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