From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Stanley <joel@jms•id.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Benjamin Herrenschmidt" <benh@kernel•crashing.org>,
"Andrew Jeffery" <andrew@aj•id.au>,
"Cédric Le Goater" <clg@kaod•org>,
"Olof Johansson" <olof@lixom•net>,
"Arnd Bergmann" <arnd@arndb•de>
Subject: Re: Please include Aspeed ARM SoC tree in linux-next
Date: Thu, 12 Jan 2017 08:17:15 +1100 [thread overview]
Message-ID: <20170112081715.59f50b35@canb.auug.org.au> (raw)
In-Reply-To: <CACPK8XcCPXWsVjufu0RAjGRjegTLuXAOHO7SbqXx8iTCJ4hbUA@mail.gmail.com>
Hi Joel,
On Wed, 11 Jan 2017 12:11:29 +1100 Joel Stanley <joel@jms•id.au> wrote:
>
> I'm the maintainer for the Aspeed ARM SoC tree and I would like it
> added to linux-next.
>
> The tree is a sub-maintainer tree for the Aspeed family of 32-bit ARM
> SoCs that went upstream earlier last year.
>
> Tree: git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
> Branch: for-next
>
> for-next is a merge of the trees that I intend to send to the ARM
> maintainers for 4.11.
>
> For now please notify just myself if something breaks.
Added from today.
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@canb•auug.org.au
prev parent reply other threads:[~2017-01-11 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 1:11 Please include Aspeed ARM SoC tree in linux-next Joel Stanley
2017-01-11 21:17 ` 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=20170112081715.59f50b35@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andrew@aj$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=clg@kaod$(echo .)org \
--cc=joel@jms$(echo .)id.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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