From: Luis Chamberlain <mcgrof@kernel.org>
To: sfr@canb.auug.org.au
Cc: petr.pavlu@suse.com, samitolvanen@google.com,
da.gomez@samsung.com, mcgrof@kernel.org,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] next: use new shared modules tree
Date: Sat, 19 Oct 2024 14:21:00 -0700 [thread overview]
Message-ID: <20241019212100.940549-1-mcgrof@kernel.org> (raw)
Use the new shared modules tree as we have more than one
modules maintainer now.
git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
Next/Trees | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Next/Trees b/Next/Trees
index 38812059087c..585cddaf8746 100644
--- a/Next/Trees
+++ b/Next/Trees
@@ -252,7 +252,7 @@ regmap git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git#for
sound git git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git#for-next
ieee1394 git https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git#for-next
sound-asoc git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git#for-next
-modules git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-next
+modules git git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git#modules-next
input git git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git#next
block git git://git.kernel.dk/linux-block.git#for-next
device-mapper git git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git#for-next
--
2.43.0
next reply other threads:[~2024-10-19 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 21:21 Luis Chamberlain [this message]
2024-10-20 10:59 ` [PATCH] next: use new shared modules tree Stephen Rothwell
2024-10-20 17:28 ` Luis Chamberlain
2024-10-20 20:39 ` 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=20241019212100.940549-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--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;
as well as URLs for NNTP newsgroup(s).