Skip to contentSkip to conversation

another branch for linux-next

DISCUSSION Christoph Hellwig 2 participants 2 messages May 13, 2018

lore
Share & tools
lore
#0 lore raw

Hi Stephen,

can you please add the for-linus branch of

git://git.infradead.org/users/hch/dma-mapping.git

to linux-next? You already carry the for-next branch, but it turns out I'll need another branch for late fixes so that for-next can remain unmerged and unrebased.

#1 lore raw

Hi Christoph,

Quoted 8 lines · On Sun, 13 May 2018 09:03:59 +0200 Christoph Hellwig <[email protected]> wrote:

can you please add the for-linus branch of

git://git.infradead.org/users/hch/dma-mapping.git

to linux-next? You already carry the for-next branch, but it turns out I'll need another branch for late fixes so that for-next can remain unmerged and unrebased.

Added from today.

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]