From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: Including Alpine -next tree in linux-next
Date: Wed, 29 Mar 2017 15:21:48 +0200 [thread overview]
Message-ID: <20170329132148.fzn4pxc4523os4y7@kwain> (raw)
In-Reply-To: <20170330001444.62ac2ad1@canb.auug.org.au>
Hi Stephen,
On Thu, Mar 30, 2017 at 12:14:54AM +1100, Stephen Rothwell wrote:
> On Wed, 29 Mar 2017 15:12:01 +0200 Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
> >
> > Hello Eric,
>
> Who is this "Eric" person? ;-)
My apologies. I completely messed up my copy-and-paste I guess... Of
course I meant "Stephen" :)
> > 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)?
The Alpine SoCs are ARM and ARM64 processors. This branch will contain
patches we plan to send to arm-soc during their merge window. So mostly
device tree and SoC specific patches.
The patches will be merged through arm-soc before getting to Linus.
Thanks,
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170329/06123696/attachment.sig>
next prev parent reply other threads:[~2017-03-29 13:21 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
2017-03-29 13:21 ` Antoine Tenart [this message]
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=20170329132148.fzn4pxc4523os4y7@kwain \
--to=antoine.tenart@free-electrons.com \
--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