From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: rafael@kernel.org, david.m.ertman@intel.com, ira.weiny@intel.com,
leon@kernel.org, aliceryhl@google.com,
daniel.almeida@collabora.com, abdiel.janulgue@gmail.com,
robin.murphy@arm.com, a.hindborg@kernel.org,
russ.weight@linux.dev, mcgrof@kernel.org, tj@kernel.org,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 2/2] MAINTAINERS: Add missing T: entry for FIRMWARE LOADER
Date: Tue, 20 Jan 2026 15:56:35 +0100 [thread overview]
Message-ID: <2026012030-contently-viewpoint-8a9b@gregkh> (raw)
In-Reply-To: <20260120123925.28267-2-dakr@kernel.org>
On Tue, Jan 20, 2026 at 01:38:53PM +0100, Danilo Krummrich wrote:
> The firmware loader is maintained through the driver-core tree, hence
> add a corresponding T: entry.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1f15d4a5b9a5..7faf04cc4278 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9830,6 +9830,7 @@ M: Russ Weight <russ.weight@linux.dev>
> M: Danilo Krummrich <dakr@kernel.org>
> L: driver-core@lists.linux.dev
> S: Maintained
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
> F: Documentation/firmware_class/
> F: drivers/base/firmware_loader/
> F: rust/kernel/firmware.rs
> --
> 2.52.0
>
>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2026-01-20 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:38 [PATCH 1/2] MAINTAINERS: Add driver-core mailing list Danilo Krummrich
2026-01-20 12:38 ` [PATCH 2/2] MAINTAINERS: Add missing T: entry for FIRMWARE LOADER Danilo Krummrich
2026-01-20 14:56 ` Greg KH [this message]
2026-01-23 12:17 ` Danilo Krummrich
2026-01-20 14:56 ` [PATCH 1/2] MAINTAINERS: Add driver-core mailing list Greg KH
2026-01-23 12:18 ` Danilo Krummrich
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=2026012030-contently-viewpoint-8a9b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=david.m.ertman@intel.com \
--cc=driver-core@lists.linux.dev \
--cc=ira.weiny@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.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