Skip to contentSkip to conversation

linux-next: add configfs-next tree in the merge

DISCUSSION Breno Leitao 4 participants 4 messages Aug 28 – Sep 28 Linux-next tree

lore
Share & tools
lore
#1 lore raw
Quoted 9 lines · Breno Leitao

I've recently become the maintainer for configfs, and now have my own tree, which I would like to see included in linux-next.

The MAINTAINERS file already has it:

T: https://git.kernel.org/pub/scm/linux/kernel/git/leitao/linux.git configfs-next

Is this enough, or do I need to take any additional steps to get this tree merged into linux-next?

Other than telling me (which you just did!) that's everything, I didn't see this mail until the merge was in progress today so today's -next still has Andreas' tree in it. I've now updated the configuration so your tree will be there from Monday.

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.

#2 lore raw

Hi Mark,

Quoted 31 lines · Mark Brown
Quoted 9 lines · Breno Leitao

I've recently become the maintainer for configfs, and now have my own tree, which I would like to see included in linux-next.

The MAINTAINERS file already has it:

T: https://git.kernel.org/pub/scm/linux/kernel/git/leitao/linux.git configfs-next

Is this enough, or do I need to take any additional steps to get this tree merged into linux-next?

Other than telling me (which you just did!) that's everything, I didn't see this mail until the merge was in progress today so today's -next still has Andreas' tree in it. I've now updated the configuration so your tree will be there from Monday.

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.

Quoted 2 lines

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.

I will PR rust related configfs changes Breno and he will send them with the rest of the C configfs changes to Linus.

Can you include my tree for the rust changes in linux-next?

CONFIGFS [RUST]
M: Andreas Hindborg <[email protected]>
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/a.hindborg/linux.git configfs-next
F: rust/kernel/configfs.rs
F: samples/rust/rust_configfs.rs

Best regards,
Andreas Hindborg

maintainer
#3 lore raw
Quoted 11 lines · Andreas Hindborg

I will PR rust related configfs changes Breno and he will send them with the rest of the C configfs changes to Linus.

Can you include my tree for the rust changes in linux-next?

CONFIGFS [RUST]
M: Andreas Hindborg <[email protected]>
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/a.hindborg/linux.git configfs-next
F: rust/kernel/configfs.rs
F: samples/rust/rust_configfs.rs

Sure, no problem - I didn't see this till I was too far into the -next merge for it to make today but I've added this now, all being well it will appear tomorrow.

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.