From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: mmotm 2020-01-28-20-05 uploaded (security/security.c)
Date: Thu, 30 Jan 2020 09:32:51 +1100 [thread overview]
Message-ID: <20200130093251.16e35ed3@canb.auug.org.au> (raw)
In-Reply-To: <56177bc4-441d-36f4-fe73-4e86edf02899@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
Hi Randy,
On Tue, 28 Jan 2020 20:52:28 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> security/security.c contains duplicate lines for <lockdown_reasons> array:
>
> Stephen, you might delete half of those for linux-next....
I did not get that in my import of mmotm today. But I actually git
merge the appropriate part of linux-next rather than applying the
linux-next.patch from mmotm - so that may have taken care of it.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-29 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 4:06 mmotm 2020-01-28-20-05 uploaded akpm
2020-01-29 4:39 ` mmotm 2020-01-28-20-05 uploaded (net/mptcp/subflow.c) Randy Dunlap
2020-01-29 4:52 ` mmotm 2020-01-28-20-05 uploaded (security/security.c) Randy Dunlap
2020-01-29 13:51 ` Paul Moore
2020-01-29 16:02 ` Randy Dunlap
2020-01-29 22:32 ` Stephen Rothwell [this message]
2020-01-29 16:43 ` mmotm 2020-01-28-20-05 uploaded (objtool warnings) Randy Dunlap
2020-01-29 17:19 ` Josh Poimboeuf
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=20200130093251.16e35ed3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.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).