From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
Casey Schaufler <casey@schaufler-ca.com>,
John Johansen <john.johansen@canonical.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH] security: mark expected switch fall-throughs
Date: Thu, 31 Jan 2019 14:30:11 -0600 [thread overview]
Message-ID: <ece10676-4ee9-bf24-ab8d-7d69a678f234@embeddedor.com> (raw)
In-Reply-To: <1548966039.6107.29.camel@linux.ibm.com>
On 1/31/19 2:20 PM, Mimi Zohar wrote:
>>>
>>> This patch touches multiple LSMs and IMA. As James has already picked
>>> up similar patches, which are in his next-general branch, perhaps he
>>> could also pick up an updated version of this one.
>>>
>>
>> Yeah. I can either integrate your recent fix and respin if you don't mind,
>> or remove the fall-through comment and wait for James to take both patches,
>> yours and mine.
>>
>> What do you prefer?
>
> Either way is fine.
>
OK. Well, I think in this case less is more, so I will integrate our changes
into a single patch.
Thanks for your feedback.
--
Gustavo
next prev parent reply other threads:[~2019-01-31 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 2:56 [PATCH] security: mark expected switch fall-throughs Gustavo A. R. Silva
2019-01-25 3:13 ` Casey Schaufler
2019-01-25 3:29 ` Gustavo A. R. Silva
2019-01-25 3:47 ` Gustavo A. R. Silva
2019-01-31 19:58 ` Mimi Zohar
2019-01-31 20:12 ` Gustavo A. R. Silva
2019-01-31 20:20 ` Mimi Zohar
2019-01-31 20:30 ` Gustavo A. R. Silva [this message]
2019-02-01 23:28 ` James Morris
2019-01-25 6:55 ` John Johansen
2019-01-25 12:37 ` Mimi Zohar
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=ece10676-4ee9-bf24-ab8d-7d69a678f234@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).