public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: Including Alpine -next tree in linux-next
Date: Thu, 30 Mar 2017 00:14:54 +1100	[thread overview]
Message-ID: <20170330001444.62ac2ad1@canb.auug.org.au> (raw)
In-Reply-To: <20170329131201.j4e7cnmgufj2i7tr@kwain>

Hi Antoine,

On Wed, 29 Mar 2017 15:12:01 +0200 Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
>
> Hello Eric,

Who is this "Eric" person? ;-)

> Would it be possible to include Alpine's -next tree in linux-next?
> 
> Repo: https://git.kernel.org/pub/scm/linux/kernel/git/atenart/linux.git
> Branch: alpine/for-next

Could you give me a short idea about what this tree contains?  Also,
whose tree will it be merged via (or does it go direct to Linus
(Torvalds)?

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-03-29 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 13:12 Including Alpine -next tree in linux-next Antoine Tenart
2017-03-29 13:14 ` Stephen Rothwell [this message]
2017-03-29 13:21   ` Antoine Tenart
2017-03-29 22:29     ` Stephen Rothwell
2017-03-30  6:24       ` Antoine Tenart

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=20170330001444.62ac2ad1@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-arm-kernel@lists.infradead.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