Skip to contentSkip to conversation

Next/Trees: update the modules tree

PATCH In review Luis Chamberlain 3 participants 5 messages Dec 8, 2021 – Dec 16, 2021 Linux-next tree

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Next/Trees: update the modules tree

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.

---
 Next/Trees | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Next/Trees +2 -2
index 1348af7fdb0f..620898543919 100644
@@ -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
Signature · 1 line
2.33.0
maintainer
#1 lore raw
Quoted 9 lines · Luis Chamberlain

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.

I just saw this - I'll roll this into my -next builds from Monday, but you should check that Stephen picks this up when he returns.

maintainer
#2 lore raw
In reply to Luis Chamberlain
Quoted 4 lines · Luis Chamberlain

pull request which was merged for v5.16-rc1. I'll queue up fixes on the modules_linus branch.

those in the modules_next branch to match parity with the same style

Actually, note that your e-mail says the branches are modules_X while the diff says modules-X which looks like it's the correct thing:

Quoted 5 lines
(quoted diff) +2 -2
-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
 
-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
#3 lore raw
Quoted 9 lines · Mark Brown
Quoted 4 lines · Luis Chamberlain

pull request which was merged for v5.16-rc1. I'll queue up fixes on the modules_linus branch.

those in the modules_next branch to match parity with the same style

Actually, note that your e-mail says the branches are modules_X while the diff says modules-X which looks like it's the correct thing:

modules-linus and modules-next are the correct ones indeed.

Sorry about the confusion.

Luis

Quoted 6 lines
Quoted 6 lines
(quoted diff) +2 -2
-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
 
-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
#4 lore raw
In reply to Luis Chamberlain

Hi Luis,

Quoted 31 lines · On Wed, 8 Dec 2021 11:59:31 -0800 Luis Chamberlain <[email protected]> wrote:

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.

---
 Next/Trees | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Next/Trees +1 -1
index 1348af7fdb0f..620898543919 100644
@@ -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

Next/Trees etnaviv git https://git.pengutronix.de/git/lst/linux#etnaviv/next · line 237

Quoted 8 lines
Next/Trees +1 -1
@@ -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

I have updated to use the new tree.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Signature · 3 lines
Cheers,
Stephen Rothwell 
[email protected]