From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
viro@zeniv.linux.org.uk
Cc: stable@vger.kernel.org, Jose Bollo <jose.bollo@iot.bzh>,
torvalds@linux-foundation.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, casey@schaufler-ca.com
Subject: Re: [PATCH] Smack: Restore the smackfsdef mount option and add missing prefixes
Date: Fri, 14 Jun 2019 16:08:11 -0700 [thread overview]
Message-ID: <cb3749a6-e45b-3e07-27f9-841adf6f4640@schaufler-ca.com> (raw)
In-Reply-To: <6cfd5113-8473-f962-dee7-e490e6f76f9c@schaufler-ca.com>
On 6/3/2019 4:07 PM, Casey Schaufler wrote:
> On 6/3/2019 3:42 PM, James Morris wrote:
>> On Fri, 31 May 2019, David Howells wrote:
>>
>>> Should this go via Al's tree, James's tree, Casey's tree or directly to Linus?
>> If it's specific to one LSM (as this is), via Casey, who can decide to
>> forward to Al or Linus.
> I would very much appreciate it if Al could send this fix along.
> I am not fully set up for sending directly to Linus.
Al, are you going to take this, or should I find another way
to get it in for 5.2?
next prev parent reply other threads:[~2019-06-14 23:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 10:53 [PATCH] Smack: Restore the smackfsdef mount option and add missing prefixes David Howells
2019-05-31 10:56 ` David Howells
2019-06-03 22:42 ` James Morris
2019-06-03 23:07 ` Casey Schaufler
2019-06-14 23:08 ` Casey Schaufler [this message]
2019-06-15 0:24 ` Linus Torvalds
2019-06-18 1:59 ` Al Viro
-- strict thread matches above, loose matches on Subject: below --
2019-05-28 20:47 David Howells
2019-05-28 21:39 ` Casey Schaufler
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=cb3749a6-e45b-3e07-27f9-841adf6f4640@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=jose.bollo@iot.bzh \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).