* Re: Request for inclusion of ep93xx tree in linux-next
2012-04-30 22:48 Request for inclusion of ep93xx tree in linux-next Ryan Mallon
@ 2012-05-01 0:27 ` Stephen Rothwell
2012-05-01 8:36 ` Arnd Bergmann
2012-06-04 5:52 ` Ryan Mallon
2 siblings, 0 replies; 7+ messages in thread
From: Stephen Rothwell @ 2012-05-01 0:27 UTC (permalink / raw)
To: Ryan Mallon
Cc: H Hartley Sweeten, Mika Westerberg, Arnd Bergmann, arm,
'linux-arm-kernel@lists•infradead.org', linux-next
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
Hi Ryan,
On Tue, 01 May 2012 08:48:09 +1000 Ryan Mallon <rmallon@gmail•com> wrote:
>
> Can you please add the following branches:
>
> ep93xx-cleanup
> ep93xx-fixes
>
> from the ep93xx git tree:
>
> git://github.com/RyanMallon/linux-ep93xx.git
>
> To linux-next. Both branches are stable and based on v3.4-rc2. Testing
> for the tree is covered by the arm ep93xx_defconfig.
I have added these from today as ep93xx-current (fixes for Linus' current
tree - branch ep93xx-fixes) and ep93xx (stuff for the next merge window -
branch ep93xx-cleanup). I have listed just you as the contact in case I
have problems (conflicts, build failures, unable to fetch etc).
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.
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
Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Request for inclusion of ep93xx tree in linux-next
2012-04-30 22:48 Request for inclusion of ep93xx tree in linux-next Ryan Mallon
2012-05-01 0:27 ` Stephen Rothwell
@ 2012-05-01 8:36 ` Arnd Bergmann
2012-05-02 6:30 ` Ryan Mallon
2012-06-04 5:52 ` Ryan Mallon
2 siblings, 1 reply; 7+ messages in thread
From: Arnd Bergmann @ 2012-05-01 8:36 UTC (permalink / raw)
To: Ryan Mallon
Cc: Stephen Rothwell, arm, Mika Westerberg, linux-next,
H Hartley Sweeten, 'linux-arm-kernel@lists•infradead.org'
On Monday 30 April 2012, Ryan Mallon wrote:
> Hi Stephen,
>
> Can you please add the following branches:
>
> ep93xx-cleanup
> ep93xx-fixes
>
> from the ep93xx git tree:
>
> git://github.com/RyanMallon/linux-ep93xx.git
>
> To linux-next. Both branches are stable and based on v3.4-rc2. Testing
> for the tree is covered by the arm ep93xx_defconfig.
>
Hi Ryan,
just for your convenience, it helps if you have only one branch that
you get included into linux-next and that combines various branches
which you intend to send to arm-soc. That frees you from the need to
notify Stephen every time you want to have another branch included.
Arnd
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Request for inclusion of ep93xx tree in linux-next
2012-04-30 22:48 Request for inclusion of ep93xx tree in linux-next Ryan Mallon
2012-05-01 0:27 ` Stephen Rothwell
2012-05-01 8:36 ` Arnd Bergmann
@ 2012-06-04 5:52 ` Ryan Mallon
2012-06-04 6:55 ` Stephen Rothwell
2 siblings, 1 reply; 7+ messages in thread
From: Ryan Mallon @ 2012-06-04 5:52 UTC (permalink / raw)
To: Stephen Rothwell, H Hartley Sweeten, Mika Westerberg,
Arnd Bergmann
Cc: arm, 'linux-arm-kernel@lists•infradead.org', linux-next
Hi Stephen,
I have ended up adding another branch to my ep93xx tree, so I have
created an ep93xx-for-next branch, which I will just merge all of
branches into. Can you please drop the ep93xx-cleanup and ep93xx-fixes
branches and just include ep93xx-for-next instead.
Thanks,
~Ryan
On 01/05/12 08:48, Ryan Mallon wrote:
> Hi Stephen,
>
> Can you please add the following branches:
>
> ep93xx-cleanup
> ep93xx-fixes
>
> from the ep93xx git tree:
>
> git://github.com/RyanMallon/linux-ep93xx.git
>
> To linux-next. Both branches are stable and based on v3.4-rc2. Testing
> for the tree is covered by the arm ep93xx_defconfig.
>
> Thanks,
> ~Ryan
^ permalink raw reply [flat|nested] 7+ messages in thread