kbuild fix branch for linux-next

kbuild fix branch for linux-next

[Nicolas Pitre]

Hello Stephen,

Could you please add the following branch to the linux-next tree:

	git://git.linaro.org/people/nicolas.pitre/linux kbuild

It includes 3 patches on top of Michal's kbuild branch already in your 
tree. Those patches fix issues that have been reported by 3 people 
already, and I'd like those fixes to appear in linux-next until Michal 
picks them up, which should happen in, well, some "undefined" amount of 
time.  ;-)


Nicolas

Re: kbuild fix branch for linux-next

[Stephen Rothwell]

Hi Nicolas,

On Mon, 25 Apr 2016 12:20:56 -0400 (EDT) Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
>
> Could you please add the following branch to the linux-next tree:
> 
> 	git://git.linaro.org/people/nicolas.pitre/linux kbuild
> 
> It includes 3 patches on top of Michal's kbuild branch already in your 
> tree. Those patches fix issues that have been reported by 3 people 
> already, and I'd like those fixes to appear in linux-next until Michal 
> picks them up, which should happen in, well, some "undefined" amount of 
> time.  ;-)

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

Re: kbuild fix branch for linux-next

[Nicolas Pitre]

On Tue, 26 Apr 2016, Stephen Rothwell wrote:

> Hi Nicolas,
> 
> On Mon, 25 Apr 2016 12:20:56 -0400 (EDT) Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> >
> > Could you please add the following branch to the linux-next tree:
> > 
> > 	git://git.linaro.org/people/nicolas.pitre/linux kbuild
> > 
> > It includes 3 patches on top of Michal's kbuild branch already in your 
> > tree. Those patches fix issues that have been reported by 3 people 
> > already, and I'd like those fixes to appear in linux-next until Michal 
> > picks them up, which should happen in, well, some "undefined" amount of 
> > time.  ;-)
> 
> Thanks for adding your subsystem tree as a participant of linux-next.

Stephen,

You may drop this branch now.  Michal was quick to pick the most 
important fixes in his branch (thanks Michal).


Nicolas

Re: kbuild fix branch for linux-next

[Stephen Rothwell]

Hi Nicolas,

On Tue, 26 Apr 2016 10:50:04 -0400 (EDT) Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
>
> On Tue, 26 Apr 2016, Stephen Rothwell wrote:
> 
> > On Mon, 25 Apr 2016 12:20:56 -0400 (EDT) Nicolas Pitre <nicolas.pitre@linaro.org> wrote:  
> > >
> > > Could you please add the following branch to the linux-next tree:
> > > 
> > > 	git://git.linaro.org/people/nicolas.pitre/linux kbuild
> > > 
> > > It includes 3 patches on top of Michal's kbuild branch already in your 
> > > tree. Those patches fix issues that have been reported by 3 people 
> > > already, and I'd like those fixes to appear in linux-next until Michal 
> > > picks them up, which should happen in, well, some "undefined" amount of 
> > > time.  ;-)  
> > 
> > Thanks for adding your subsystem tree as a participant of linux-next.  
> 
> You may drop this branch now.  Michal was quick to pick the most 
> important fixes in his branch (thanks Michal).

Thanks, will do.

-- 
Cheers,
Stephen Rothwell