From: Simon Horman <horms@verge•net.au>
To: Stephen Rothwell <sfr@canb•auug.org.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: Tue, 6 Oct 2015 09:25:21 +0900 [thread overview]
Message-ID: <20151006002521.GA12506@verge.net.au> (raw)
In-Reply-To: <20151005234054.1bfade21@canb.auug.org.au>
On Mon, Oct 05, 2015 at 11:40:54PM +1100, Stephen Rothwell wrote:
> 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 ...)
Thanks, noted.
> 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.
Sorry for not being clearer about the branch; yes, the master branch is
the one to fetch.
> 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.
prev parent reply other threads:[~2015-10-06 0:25 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
2015-10-06 0:25 ` Simon Horman [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=20151006002521.GA12506@verge.net.au \
--to=horms@verge$(echo .)net.au \
--cc=davem@davemloft$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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