From: Sahil Chandna <chandna.sahil@gmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
lorenzo.stoakes@oracle.com, mhocko@suse.com, vbabka@suse.cz,
rppt@kernel.org, surenb@google.com, hannes@cmpxchg.org,
shakeel.butt@linux.dev, zhengqi.arch@bytedance.com,
Liam.Howlett@oracle.com, weixugc@google.com,
axelrasmussen@google.com, yuanchu@google.com,
yosry.ahmed@linux.dev, nphamcs@gmail.com,
chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Sahil Chandna <chandna.sahil@gmail.com>
Subject: [PATCH v2 0/3] mm: Coccinelle-driven cleanups across memory management code
Date: Sun, 23 Nov 2025 08:34:15 +0530 [thread overview]
Message-ID: <cover.1763796152.git.chandna.sahil@gmail.com> (raw)
This patch series contains three minor cleanups identified by
Coccinelle scripts under scripts/coccinelle/misc/:
* Replace manual ternary expression with the min() macro in pagewalk.c
and change return expression for clarity.
* Use the %pe printk format specifier for PTR_ERR() reporting
in vmscan.c and zswap.c
Found using:
make coccicheck MODE=report M=mm/
changes in v2:
- Patch 1/3: update return value as per review comments.
- patch 2/3 and 3/3: Add Acked-by and Reviewed-by tags.
link to v1: https://lore.kernel.org/all/cover.1763227530.git.chandna.sahil@gmail.com/
Sahil Chandna (3):
mm: pagewalk: simplify hugepage boundary calculation using min()
mm/vmscan: use %pe to print error pointers
mm/zswap: use %pe to print error pointers
mm/pagewalk.c | 3 +--
mm/vmscan.c | 4 ++--
mm/zswap.c | 4 ++--
3 files changed, 5 insertions(+), 6 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-23 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 3:04 Sahil Chandna [this message]
2025-11-23 3:04 ` [PATCH v2 1/3] mm: pagewalk: simplify hugepage boundary calculation using min() Sahil Chandna
2025-11-24 10:53 ` David Hildenbrand (Red Hat)
2025-11-23 3:04 ` [PATCH v2 2/3] mm/vmscan: use %pe to print error pointers Sahil Chandna
2025-11-24 10:54 ` David Hildenbrand (Red Hat)
2025-11-23 3:04 ` [PATCH v2 3/3] mm/zswap: " Sahil Chandna
2025-11-24 10:54 ` David Hildenbrand (Red Hat)
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=cover.1763796152.git.chandna.sahil@gmail.com \
--to=chandna.sahil@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=yosry.ahmed@linux.dev \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.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