Re: Including C6X in linux-next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mark,

On Thu, 06 Oct 2011 20:25:30 -0400 Mark Salter <msalter@xxxxxxxxxx> wrote:
>
> On Fri, 2011-10-07 at 10:29 +1100, Stephen Rothwell wrote:
> > 
> > On Thu, 06 Oct 2011 12:04:44 -0400 Mark Salter <msalter@xxxxxxxxxx> wrote:
> > >
> > > All of the patches in the latest C6X patch set have gotten Acked-bys, so
> > > I guess its time to include it in the linux-next tree. The patches are
> > > available on the "for-linux-next" branch at:
> > > 
> > >    http://linux-c6x.org/git/projects/linux-c6x-upstreaming.git
> > 
> > I had a look at this and unfortunately you have based it on linux-next.
> > I cannot use it like that.  You need to rebase this onto Linus' tree,
> > sorry.  (Also, I used the git://... version of the URL as that is more
> > efficient than http://.. for updting git trees).
> 
> Okay, it is now rebased on Linus' tree.

I have added this tree from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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@xxxxxxxxxxxxxxxx

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Attachment: pgphHowglXwmU.pgp
Description: PGP signature


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux