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

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership•com>
Cc: linux-next@vger•kernel.org, linux-fsdevel@vger•kernel.org,
	Linux Containers <containers@lists•linux-foundation.org>
Subject: Re: Can you add the binfmt_misc tree to linux-next?
Date: Tue, 28 Jun 2016 09:29:14 +1000	[thread overview]
Message-ID: <20160628092914.7ab1b37e@canb.auug.org.au> (raw)
In-Reply-To: <1467044198.2264.19.camel@HansenPartnership.com>

Hi James,

On Mon, 27 Jun 2016 09:16:38 -0700 James Bottomley <James.Bottomley@HansenPartnership•com> wrote:
>
> Since I'd effectively become binfmt_misc maintainer when these patches
> get merged on the last person to touch it owns it principle, it makes
> sense to begin now more formally.  The tree is at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/binfmt_misc.git for-next
> 
> It currently contains four patches adding the container emulation
> infrastructure from the persistent-handlers branch.

Added from today.  I only found 3 patches, though:

4af75df6a410 binfmt_misc: add F option description to documentation
948b701a607f binfmt_misc: add persistent opened binary handler for containers
9a08c352d053 fs: add filp_clone_open API

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

next prev parent reply	other threads:[~2016-06-27 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 16:16 Can you add the binfmt_misc tree to linux-next? James Bottomley
2016-06-27 23:29 ` Stephen Rothwell [this message]
2016-06-27 23:57   ` James Bottomley

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=20160628092914.7ab1b37e@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=James.Bottomley@HansenPartnership$(echo .)com \
    --cc=containers@lists$(echo .)linux-foundation.org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.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