From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mimi Zohar <zohar@linux•vnet.ibm.com>
Cc: linux-next <linux-next@vger•kernel.org>,
linux-security-module <linux-security-module@vger•kernel.org>
Subject: Re: linux-integrity
Date: Fri, 6 Jun 2014 17:56:29 +1000 [thread overview]
Message-ID: <20140606175629.11d3b96d@canb.auug.org.au> (raw)
In-Reply-To: <1402031469.5458.162.camel@dhcp-9-2-203-236.watson.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
Hi Mimi,
On Fri, 06 Jun 2014 01:11:09 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> On Fri, 2014-06-06 at 14:22 +1000, Stephen Rothwell wrote:
> >
> > 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
>
> The linux-integrity measures, appraises and enforces local file
> integrity, and audit logs file hashes based on policy. The
> linux-integrity subsystem is upstreamed and pulled into linux-next via
> linux-security. A suggestion was made to have the linux-integrity
> subsystem pulled directly into linux-next.
>
> > ... 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 ...
>
> 8 patches, mostly bugs fixes, are queued to be upstreamed
> http://marc.info/?l=linux-security-module&m=140128032831578&w=2
> Please add the linux-integrity subsystem at the next feasible
> opportunity.
Added from Tuesday. I have just you listed as the contact in case of
problems with the tree - let me know if anyone else should also be
informed.
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 7:56 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 ` linux-integrity Stephen Rothwell
2014-06-06 5:11 ` linux-integrity Mimi Zohar
2014-06-06 7:21 ` linux-integrity Stephen Rothwell
2014-06-06 7:56 ` Stephen Rothwell [this message]
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=20140606175629.11d3b96d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-security-module@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
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