From: Luis Chamberlain <mcgrof@kernel.org>
To: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
mcgrof@kernel.org, jeyu@kernel.org,
mcgrof@bombadil.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Next/Trees: update the modules tree
Date: Wed, 8 Dec 2021 11:59:31 -0800 [thread overview]
Message-ID: <20211208195931.3369500-1-mcgrof@kernel.org> (raw)
Upon Jessica's request I'm helping with modules maintenance
so this patch reflect this and updates the trees to mine. For
the last v5.16 merge window I have already sent my first
pull request which was merged for v5.16-rc1. I'll queue up fixes
on the modules_linus branch.
I'm now queuing up changes for the next release and so will be putting
those in the modules_next branch to match parity with the same style
used by Jessica.
Cc: Jessica Yu <jeyu@kernel.org>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
Next/Trees | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Next/Trees b/Next/Trees
index 1348af7fdb0f..620898543919 100644
--- a/Next/Trees
+++ b/Next/Trees
@@ -46,7 +46,7 @@ input-current git git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git#f
crypto-current git git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git#master
vfio-fixes git git://github.com/awilliam/linux-vfio.git#for-linus
kselftest-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git#fixes
-modules-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git#modules-linus
+modules-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
dmaengine-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git#fixes
backlight-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git#for-backlight-fixes
mtd-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git#mtd/fixes
@@ -231,7 +231,7 @@ etnaviv git https://git.pengutronix.de/git/lst/linux#etnaviv/next
regmap git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git#for-next
sound git git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.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/jeyu/linux.git#modules-next
+modules git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/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.33.0
next reply other threads:[~2021-12-08 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 19:59 Luis Chamberlain [this message]
2021-12-10 21:30 ` [PATCH] Next/Trees: update the modules tree Mark Brown
2021-12-10 21:38 ` Mark Brown
2021-12-10 21:56 ` Luis Chamberlain
2021-12-16 12:16 ` 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=20211208195931.3369500-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mcgrof@bombadil.infradead.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