[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160427011937.13a339e9@canb.auug.org.au>
Date: Wed, 27 Apr 2016 01:19:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: Michal Marek <mmarek@...e.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: kbuild fix branch for linux-next
Hi Nicolas,
On Tue, 26 Apr 2016 10:50:04 -0400 (EDT) Nicolas Pitre <nicolas.pitre@...aro.org> wrote:
>
> On Tue, 26 Apr 2016, Stephen Rothwell wrote:
>
> > On Mon, 25 Apr 2016 12:20:56 -0400 (EDT) Nicolas Pitre <nicolas.pitre@...aro.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
Powered by blists - more mailing lists