linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Please add reset/next and reset/fixes to linux-next
@ 2017-05-29 13:23 Philipp Zabel
  2017-05-30  4:26 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Philipp Zabel @ 2017-05-29 13:23 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, kernel

Hi Stephen,

could you add the reset/next and reset/fixes branches to the linux-next
tree? I use those to stage reset framework and driver patches before
sending them off to be merged via arm-soc.

https://git.pengutronix.de/git/pza/linux reset/fixes
https://git.pengutronix.de/git/pza/linux reset/next

regards
Philipp

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Please add reset/next and reset/fixes to linux-next
  2017-05-29 13:23 Please add reset/next and reset/fixes to linux-next Philipp Zabel
@ 2017-05-30  4:26 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2017-05-30  4:26 UTC (permalink / raw)
  To: Philipp Zabel; +Cc: linux-next, kernel

Hi Philipp,

On Mon, 29 May 2017 15:23:17 +0200 Philipp Zabel <p.zabel@pengutronix.de> wrote:
>
> could you add the reset/next and reset/fixes branches to the linux-next
> tree? I use those to stage reset framework and driver patches before
> sending them off to be merged via arm-soc.
> 
> https://git.pengutronix.de/git/pza/linux reset/fixes
> https://git.pengutronix.de/git/pza/linux reset/next

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-05-30  4:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-29 13:23 Please add reset/next and reset/fixes to linux-next Philipp Zabel
2017-05-30  4:26 ` Stephen Rothwell

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).