From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kbuild fix branch for linux-next
Date: Wed, 27 Apr 2016 01:19:37 +1000 [thread overview]
Message-ID: <20160427011937.13a339e9@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.20.1604261047530.5091@knanqh.ubzr>
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
prev parent reply other threads:[~2016-04-26 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 16:20 Nicolas Pitre
2016-04-25 22:57 ` Stephen Rothwell
2016-04-26 14:50 ` Nicolas Pitre
2016-04-26 15:19 ` Stephen Rothwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160427011937.13a339e9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.pitre@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®