From: Casey Schaufler <casey@schaufler-ca.com>
To: Linux Security Module list <linux-security-module@vger.kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>,
John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
casey@schaufler-ca.com
Subject: Stacking patches for 5.3
Date: Fri, 24 May 2019 12:26:30 -0700 [thread overview]
Message-ID: <1106985e-1620-75b2-d6bf-c2c95d9a0fbb@schaufler-ca.com> (raw)
I have a set of 59 patches for the nest round of LSM stacking.
They are all really small. Kees has expressed a preference for
small patches. I think that the collapsed set of about 10 would
make more sense. Which would the community as a whole prefer?
The patches are not much different from what has been presented
already.
next reply other threads:[~2019-05-24 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 19:26 Casey Schaufler [this message]
2019-05-24 19:36 ` Stacking patches for 5.3 James Morris
2019-05-24 19:37 ` Paul Moore
2019-05-24 19:55 ` Casey Schaufler
2019-05-25 3:55 ` James Morris
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=1106985e-1620-75b2-d6bf-c2c95d9a0fbb@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.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