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

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mimi Zohar <zohar@linux•vnet.ibm.com>
Cc: linux-next <linux-next@vger•kernel.org>
Subject: Re: linux-integrity
Date: Fri, 6 Jun 2014 14:22:55 +1000	[thread overview]
Message-ID: <20140606142255.76bc38f1@canb.auug.org.au> (raw)
In-Reply-To: <1402026956.5458.130.camel@dhcp-9-2-203-236.watson.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

Hi Mimi,

On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> Please include
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> #next in linux-next.

OK, it would be good to know what that tree is about ... also it is
really late for inclusion in v3.16 even - I generally do not add trees
to linux-next during the merge window.  This does not mean I won't
include it if you can convince me otherwise ...

Also, you should cc this request to people/mailing lists that may have
a stake or interest in what the tree contains and consider these things
about inclusion:

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

next prev parent reply	other threads:[~2014-06-06  4:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  3:55 linux-integrity Mimi Zohar
2014-06-06  4:22 ` Stephen Rothwell [this message]
2014-06-06  5:11   ` linux-integrity Mimi Zohar
2014-06-06  7:21     ` linux-integrity Stephen Rothwell
2014-06-06  7:56     ` linux-integrity Stephen Rothwell
2014-06-06 11:43       ` linux-integrity Mimi Zohar
2014-06-06 14:20         ` linux-integrity Stephen Rothwell

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=20140606142255.76bc38f1@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=zohar@linux$(echo .)vnet.ibm.com \
    /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