From: Nathan Chancellor <nathan@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicolas Schier <nsc@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Updating Kbuild tree and contacts
Date: Mon, 11 Aug 2025 11:48:49 -0700 [thread overview]
Message-ID: <20250811184849.GA1266@ax162> (raw)
Hi Stephen,
Nicolas and I have taken over Kbuild maintenace from Masahiro as of
commit 8d6841d5cb20 ("MAINTAINERS: hand over Kbuild maintenance"). Could
you please update your contacts for the Kbuild tree to both of us and
the Kbuild tree to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git
and start pulling kbuild-fixes and kbuild-next in at their respective
places within the -next update cycle? Please let me know if there are
any issues or questions.
Cheers,
Nathan
next reply other threads:[~2025-08-11 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 18:48 Nathan Chancellor [this message]
2025-08-11 22:34 ` Updating Kbuild tree and contacts Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 21:34 Nicolas Schier
2025-12-19 9:44 ` Stephen Rothwell
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=20250811184849.GA1266@ax162 \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nsc@kernel.org \
--cc=sfr@canb.auug.org.au \
/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