From: Ben Dooks <ben-linux@fluff.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-next@vger.kernel.org, Jean Delvare <khali@linux-fr.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: tree addition request
Date: Tue, 24 Nov 2009 09:28:03 +0000 [thread overview]
Message-ID: <20091124092803.GN23772@trinity.fluff.org> (raw)
In-Reply-To: <20091124105114.2149e4a0.sfr@canb.auug.org.au>
On Tue, Nov 24, 2009 at 10:51:14AM +1100, Stephen Rothwell wrote:
> Hi Ben,
>
> On Mon, 23 Nov 2009 22:30:44 +0000 Ben Dooks <ben-linux@fluff.org> wrote:
> >
> > Is this the right place to request adding one/two trees to linux-next?
>
> Yep.
>
> > git://git.fluff.org/bjdooks/linux.git next-i2c
>
> I already have an i2c quilt series from Jean Delvare
> <khali@linux-fr.org>, how does this relate to that?
I've been doing the more 'embedded' side of things, which means generally
the non-X86 side of things such as ARM, MIPS, etc. for the last couple of
releases.
> > git://git.fluff.org/bjdooks/linux.git next-samsung
>
> This is a set of arm platforms, right?
This is the ARM support for a number of Samsung SoC/processors that
i've been maintaining for a long time now. A number of people have
requested these trees be included in -next now that the non-core ARM
code is being submitted directly to linus.
> I have added both these trees from today, assuming there are no
> objections. I have called them bjdooks-i2c and sumsung respectively.
>
> Thanks for adding your subsystem tree as a participant of linux-next. As
> you may know, this is not a judgment 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.
Yes.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
prev parent reply other threads:[~2009-11-24 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 22:30 tree addition request Ben Dooks
2009-11-23 23:51 ` Stephen Rothwell
2009-11-24 7:39 ` Jean Delvare
2009-11-24 7:41 ` Stephen Rothwell
2009-11-24 9:28 ` Ben Dooks [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=20091124092803.GN23772@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).