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-integrity <linux-integrity@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>,
James Morris <jmorris@namei.org>
Subject: Re: ima: temporary "next-queued-testing" branch (UPDATE)
Date: Tue, 19 Dec 2017 07:43:50 +1100 [thread overview]
Message-ID: <20171219074350.6974d1b6@canb.auug.org.au> (raw)
In-Reply-To: <1513611047.5221.18.camel@linux.vnet.ibm.com>
Hi Mimi,
On Mon, 18 Dec 2017 10:30:47 -0500 Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> As the integrity subsystem is now back in sync with the security tree,
> I'd really appreciate if you could include the integrity tree in
> linux-next. Instead of including the integrity "next" branch as
> previously, could you include the "next-integrity" branch instead?
Done.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-12-18 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512564458.4698.33.camel@linux.vnet.ibm.com>
[not found] ` <1513029726.3530.29.camel@linux.vnet.ibm.com>
2017-12-18 15:30 ` ima: temporary "next-queued-testing" branch (UPDATE) Mimi Zohar
2017-12-18 20:43 ` Stephen Rothwell [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=20171219074350.6974d1b6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).