From: Sahil Chandna <chandna.sahil@gmail.com>
To: akpm@linux-foundation.org, hannes@cmpxchg.org,
yosry.ahmed@linux.dev, nphamcs@gmail.com, david@kernel.org,
sj@kernel.org, mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
axelrasmussen@google.com, yuanchu@google.com, weixugc@google.com,
chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Sahil Chandna <chandna.sahil@gmail.com>
Subject: [PATCH v5 0/2] mm: Coccinelle-driven cleanups across memory
Date: Thu, 5 Feb 2026 00:24:06 +0530 [thread overview]
Message-ID: <cover.1770230135.git.chandna.sahil@gmail.com> (raw)
This patch series contains minor changes identified by
Coccinelle scripts under scripts/coccinelle/misc/:
* Use the %pe printk format specifier for PTR_ERR() reporting
in vmscan.c and zswap.c
Found using:
make coccicheck MODE=report M=mm/
change since v4:
- Remove use of ALIGN() macro as it caused infinite loop in case page
was already aligned.
change since v3:
- Update the commit message to highlight change in computation of
boundary using ALIGN().
changes since v1 and 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/
link to v2: https://lore.kernel.org/all/cover.1763796152.git.chandna.sahil@gmail.com/
link to v3: https://lore.kernel.org/all/cover.1764177933.git.chandna.sahil@gmail.com/
link to v4: https://lore.kernel.org/all/cover.1764312627.git.chandna.sahil@gmail.com/
Sahil Chandna (2):
mm/vmscan: use %pe to print error pointers
mm/zswap: use %pe to print error pointers
mm/vmscan.c | 4 ++--
mm/zswap.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.50.1
next reply other threads:[~2026-02-04 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:54 Sahil Chandna [this message]
2026-02-04 18:54 ` [PATCH v5 1/2] mm/vmscan: use %pe to print error pointers Sahil Chandna
2026-02-04 18:54 ` [PATCH v5 2/2] mm/zswap: " Sahil Chandna
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.1770230135.git.chandna.sahil@gmail.com \
--to=chandna.sahil@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--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