From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, minchan@kernel.org,
mm-commits@vger.kernel.org
Subject: [folded-merged] mm-support-vector-address-ranges-for-process_madvise-fix-fix-fix-fix-fix.patch removed from -mm tree
Date: Wed, 10 Jun 2020 18:24:08 -0700 [thread overview]
Message-ID: <20200611012408._We-3yqp3%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm-support-vector-address-ranges-for-process_madvise-fix-fix-fix-fix-fix
has been removed from the -mm tree. Its filename was
mm-support-vector-address-ranges-for-process_madvise-fix-fix-fix-fix-fix.patch
This patch was dropped because it was folded into mm-support-vector-address-ranges-for-process_madvise.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-support-vector-address-ranges-for-process_madvise-fix-fix-fix-fix-fix
add compat_sys_process_madvise to mips syscall table
Cc: Minchan Kim <minchan@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/mips/kernel/syscalls/syscall_o32.tbl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/mips/kernel/syscalls/syscall_o32.tbl~mm-support-vector-address-ranges-for-process_madvise-fix-fix-fix-fix-fix
+++ a/arch/mips/kernel/syscalls/syscall_o32.tbl
@@ -426,4 +426,4 @@
437 o32 openat2 sys_openat2
438 o32 pidfd_getfd sys_pidfd_getfd
439 o32 faccessat2 sys_faccessat2
-440 o32 process_madvise sys_process_madvise
+440 o32 process_madvise sys_process_madvise compat_sys_process_madvise
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-pass-task-and-mm-to-do_madvise.patch
mm-support-vector-address-ranges-for-process_madvise.patch
arch-powerpc-mm-pgtablec-another-missed-conversion.patch
drivers-tty-serial-sh-scic-suppress-uninitialized-var-warning.patch
mm.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2020-06-11 1:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200611012408._We-3yqp3%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
/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).