From: jeffxu@chromium.org
To: akpm@linux-foundation.org, vbabka@suse.cz,
lorenzo.stoakes@oracle.com, Liam.Howlett@Oracle.com
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-mm@kvack.org, jorgelo@chromium.org, keescook@chromium.org,
pedro.falcato@gmail.com, rdunlap@infradead.org,
Jeff Xu <jeffxu@chromium.org>
Subject: [PATCH v2 0/1] remove can_do_mseal
Date: Fri, 6 Dec 2024 19:48:38 +0000 [thread overview]
Message-ID: <20241206194839.3030596-1-jeffxu@google.com> (raw)
From: Jeff Xu <jeffxu@chromium.org>
History:
V2: remove the can_do_mseal (Liam.Howlett, Lorenzo Stoakes)
V1: initial version.
Jeff Xu (1):
mseal: move can_do_mseal() to mseal.c
mm/internal.h | 16 ----------------
mm/mseal.c | 6 +++---
2 files changed, 3 insertions(+), 19 deletions(-)
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-12-06 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 19:48 jeffxu [this message]
2024-12-06 19:48 ` [PATCH v2 1/1] mseal: remove can_do_mseal() jeffxu
2024-12-06 19:56 ` Lorenzo Stoakes
2024-12-06 20:08 ` Jeff Xu
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=20241206194839.3030596-1-jeffxu@google.com \
--to=jeffxu@chromium.org \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pedro.falcato@gmail.com \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
/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