From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linux Security Module list
<linux-security-module@vger.kernel.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [PULL] Smack: one more change for 5.2
Date: Wed, 1 May 2019 02:08:21 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1905010208030.32268@namei.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1905010207400.32268@namei.org>
On Wed, 1 May 2019, James Morris wrote:
> Applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
That should be next-smack.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-04-30 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 0:38 [PULL] Smack: one more change for 5.2 Casey Schaufler
2019-04-30 16:07 ` James Morris
2019-04-30 16:08 ` James Morris [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=alpine.LRH.2.21.1905010208030.32268@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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