[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130108145922.58ab8ad4796076c9d14b6197@canb.auug.org.au>
Date: Tue, 8 Jan 2013 14:59:22 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Casey Schaufler <casey@...aufler-ca.com>
Cc: James Morris <jmorris@...ei.org>,
LSM <linux-security-module@...r.kernel.org>,
LKLM <linux-kernel@...r.kernel.org>,
SE Linux <selinux@...ho.nsa.gov>,
John Johansen <john.johansen@...onical.com>,
Eric Paris <eparis@...hat.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Kees Cook <keescook@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v12 0/9] LSM: Multiple concurrent LSMs
Hi Casey,
On Tue, 8 Jan 2013 14:01:59 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Let me ask Andrew's question: Why do you want to do this (what is the
> use case)? What does this gain us?
>
> Also, you should use unique subjects for each of the patches in the
> series.
You probably also want to think a bit harder about the order of the
patches - you should introduce new APIs before you use them and remove
calls to functions before you remove the functions.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists