public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-next@vger.kernel.org, kernel@pengutronix.de
Subject: Re: Please add reset/next and reset/fixes to linux-next
Date: Tue, 30 May 2017 14:26:08 +1000	[thread overview]
Message-ID: <20170530142608.0eb6fd7e@canb.auug.org.au> (raw)
In-Reply-To: <1496064197.17695.72.camel@pengutronix.de>

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

      reply	other threads:[~2017-05-30  4:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=20170530142608.0eb6fd7e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kernel@pengutronix.de \
    --cc=linux-next@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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