From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Linux Security Module list
<linux-security-module@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>,
John Johansen <john.johansen@canonical.com>
Subject: Re: Stacking patches for 5.3
Date: Fri, 24 May 2019 12:55:11 -0700 [thread overview]
Message-ID: <e42136b0-d656-1aa9-c848-d6a8aaa48c92@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhRY8UOS9G_CgBPe=tVYgLmL7KHC_=RRtHyemHrx0_RqjA@mail.gmail.com>
On 5/24/2019 12:37 PM, Paul Moore wrote:
> On Fri, May 24, 2019 at 3:26 PM Casey Schaufler <casey@schaufler-ca.com> wrote:
>> 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.
> Is there an option for "not posted on the Friday before a holiday weekend"? ;)
I'm waiting for James' next-general to base it on, so you needn't worry.
> I honestly don't care too much about patch size, regardless of how it
> is packaged it's a lot of pretty critical stuff to review.
Consensus looks like small patches are the way to go. So be it.
next prev parent reply other threads:[~2019-05-24 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 19:26 Stacking patches for 5.3 Casey Schaufler
2019-05-24 19:36 ` James Morris
2019-05-24 19:37 ` Paul Moore
2019-05-24 19:55 ` Casey Schaufler [this message]
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=e42136b0-d656-1aa9-c848-d6a8aaa48c92@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