[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170329132148.fzn4pxc4523os4y7@kwain>
Date: Wed, 29 Mar 2017 15:21:48 +0200
From: Antoine Tenart <antoine.tenart@...e-electrons.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Antoine Tenart <antoine.tenart@...e-electrons.com>,
tsahee@...apurnalabs.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: Including Alpine -next tree in linux-next
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@...e-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
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists