From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,lorenzo.stoakes@oracle.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-madvise-split-out-mmap-locking-operations-for-madvise-fix-checkpatch-fixes.patch removed from -mm tree
Date: Sun, 16 Mar 2025 21:31:06 -0700 [thread overview]
Message-ID: <20250317043106.D1C00C4CEEC@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-madvise-split-out-mmap-locking-operations-for-madvise-fix-checkpatch-fixes
has been removed from the -mm tree. Its filename was
mm-madvise-split-out-mmap-locking-operations-for-madvise-fix-checkpatch-fixes.patch
This patch was dropped because it was folded into mm-madvise-split-out-mmap-locking-operations-for-madvise.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-madvise-split-out-mmap-locking-operations-for-madvise-fix-checkpatch-fixes
Date: Tue Feb 11 03:55:07 PM PST 2025
WARNING: suspect code indent for conditional statements (8, 12)
#57: FILE: mm/madvise.c:1598:
+ if (is_memory_failure(behavior))
+ return 0;
WARNING: Statements should start on a tabstop
#58: FILE: mm/madvise.c:1599:
+ return 0;
WARNING: suspect code indent for conditional statements (8, 12)
#72: FILE: mm/madvise.c:1612:
+ if (is_memory_failure(behavior))
+ return;
WARNING: Statements should start on a tabstop
#73: FILE: mm/madvise.c:1613:
+ return;
Please run checkpatch prior to sending patches
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/madvise.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/madvise.c~mm-madvise-split-out-mmap-locking-operations-for-madvise-fix-checkpatch-fixes
+++ a/mm/madvise.c
@@ -1596,7 +1596,7 @@ static bool is_memory_failure(int behavi
static int madvise_lock(struct mm_struct *mm, int behavior)
{
if (is_memory_failure(behavior))
- return 0;
+ return 0;
if (madvise_need_mmap_write(behavior)) {
if (mmap_write_lock_killable(mm))
@@ -1610,7 +1610,7 @@ static int madvise_lock(struct mm_struct
static void madvise_unlock(struct mm_struct *mm, int behavior)
{
if (is_memory_failure(behavior))
- return;
+ return;
if (madvise_need_mmap_write(behavior))
mmap_write_unlock(mm);
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-madvise-split-out-mmap-locking-operations-for-madvise.patch
mm-madvise-remove-redundant-mmap_lock-operations-from-process_madvise-fix.patch
mm-hugetlb-add-hugetlb_alloc_threads-cmdline-option-fix.patch
mm-pgtable-convert-some-architectures-to-use-tlb_remove_ptdesc-v2-fix.patch
lib-plistc-add-shortcut-for-plist_requeue-fix.patch
scsi-lpfc-convert-timeouts-to-secs_to_jiffies-fix.patch
signal-avoid-clearing-tif_sigpending-in-recalc_sigpending-if-unset-fix.patch
hung_task-show-the-blocker-task-if-the-task-is-hung-on-mutex-fix.patch
reply other threads:[~2025-03-17 4:31 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=20250317043106.D1C00C4CEEC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=lorenzo.stoakes@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.