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 09:29:09 +1100 [thread overview]
Message-ID: <20170330092902.49cb4d4f@canb.auug.org.au> (raw)
In-Reply-To: <20170329132148.fzn4pxc4523os4y7@kwain>
Hi Antoine,
On Wed, 29 Mar 2017 15:21:48 +0200 Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
>
> 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" :)
No worries :-)
> > > 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.
Included from today with just you as the contact.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr at canb.auug.org.au
next prev parent reply other threads:[~2017-03-29 22:29 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
2017-03-29 22:29 ` Stephen Rothwell [this message]
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=20170330092902.49cb4d4f@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