public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Simon Horman <horms@verge•net.au>
Cc: linux-next@vger•kernel.org,
	Pablo Neira Ayuso <pablo@netfilter•org>,
	David Miller <davem@davemloft•net>
Subject: Re: Request for inclusion of ipvs and ipvs-next trees in next
Date: Mon, 5 Oct 2015 23:40:54 +1100	[thread overview]
Message-ID: <20151005234054.1bfade21@canb.auug.org.au> (raw)
In-Reply-To: <20151002005626.GA4802@verge.net.au>

Hi Simon,

On Fri, 2 Oct 2015 09:56:26 +0900 Simon Horman <horms@verge•net.au> wrote:
>
> I would like to request the inclusion of 'ipvs.git' and 'ipvs-next.git' in
> linux-next.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git
> 
> I have been maintaining IPVS using those trees for a number of years and
> maintaining IPVS without those trees for a number of years before that.
> 
> Usually 'ipvs-next.git' feeds into Pablo's 'nf-next.git' which
> in turn feeds into Dave's 'net-next.git'. Likewise for s/-next//.

Added from tomorrow.  (just noting that I don't fetch the nf{,-next}
trees ...)

I am using the git:... version of the URLs and assume that you mean for me
to fetch the master branch of each of those trees.

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

next prev parent reply	other threads:[~2015-10-05 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  0:56 Request for inclusion of ipvs and ipvs-next trees in next Simon Horman
2015-10-05 12:40 ` Stephen Rothwell [this message]
2015-10-06  0:25   ` Simon Horman

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=20151005234054.1bfade21@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=horms@verge$(echo .)net.au \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=pablo@netfilter$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox