Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1448722 > unrolled thread

Adding linux-sh (arch/sh) to linux-next

Back to article view | Back to linux.kernel

Contents

  Adding linux-sh (arch/sh) to linux-next Rich Felker <dalias@libc.org> - 2016-07-22 20:40 +0200
    Re: Adding linux-sh (arch/sh) to linux-next Stephen Rothwell <sfr@canb.auug.org.au> - 2016-07-24 02:30 +0200

#1448722 — Adding linux-sh (arch/sh) to linux-next

Hi Stephen,

Can you please add the linux-sh tree's for-next branch to be pulled
for linux-next?

	git://git.libc.org/linux-sh for-next

Let me know if anything's wrong with how it's set up. I'm new to
linux-next (and still fairly new to arch maintainership) so apologies
if I missed anything. I do plan to move the tree to kernel.org,
hopefully soon, but I'm still waiting on people who promised to sign
my keys so for the time being it's still on libc.org.

Rich

[toc] | [next] | [standalone]

#1449024

Hi Rich,

On Fri, 22 Jul 2016 14:30:06 -0400 Rich Felker <dalias@libc.org> wrote:
>
> Can you please add the linux-sh tree's for-next branch to be pulled
> for linux-next?
> 
> 	git://git.libc.org/linux-sh for-next
> 
> Let me know if anything's wrong with how it's set up. I'm new to
> linux-next (and still fairly new to arch maintainership) so apologies
> if I missed anything. I do plan to move the tree to kernel.org,
> hopefully soon, but I'm still waiting on people who promised to sign
> my keys so for the time being it's still on libc.org.

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.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web