From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Christos Skarlos <christosskarlos.kernel@gmail.com>,
akpm@linux-foundation.org, david@kernel.org,
muchun.song@linux.dev, osalvador@suse.de, ljs@kernel.org,
hannes@cmpxchg.org
Cc: ziy@nvidia.com, baolin.wang@linux.alibaba.com,
liam@infradead.org, nico.pache@linux.dev, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, lance.yang@linux.dev,
usama.arif@linux.dev, kas@kernel.org, jannh@google.com,
pfalcato@suse.de, kasong@tencent.com, qi.zheng@linux.dev,
shakeel.butt@linux.dev, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, mhocko@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] mm: minor janitorial style cleanups
Date: Mon, 7 Sep 2026 09:43:58 +0200 [thread overview]
Message-ID: <60a8cf51-1493-4dbd-8779-8f007f6783a0@kernel.org> (raw)
In-Reply-To: <20260905183135.20993-1-christosskarlos.kernel@gmail.com>
On 9/5/26 20:31, Christos Skarlos wrote:
> This patch series resolves various coding style issues flagged by
> checkpatch.pl across mmap.c , vmscan.c and hugetlb.c.
Checkpatch is meant for avoiding the issues when submitting new patches, not
to be run on the existing code to generate fixes just for the checkpatch
issues. NAK
> Changes in v2:
> - Restored filename comment at the top of mmap.c.
> - Restore <asm/...> headers in mmap.c as they are architecture-specific.
> - Remove blank lines above VMA_ITERATORS and NODEMASK_ALLOC declarations.
> - Fixed commit message typos.
>
>
> Thanks for the thorough review and guidance. As a newcomer every
> feedback and advice is really valuable to my workflow.
>
> (Note: Apologies for the stray huge_memory.c patch included in v1 by
> accident; this v2 series correctly focuses strictly on mmap, vmscan, and hugetlb.)
>
> No functional changes are introduced.
>
> Christos Skarlos (3):
> mm/mmap: fix various coding style warnings
> mm/vmscan: fix various coding style warnings and errors
> mm/hugetlb: fix various coding style warnings.
>
> mm/hugetlb.c | 16 ++++++++++------
> mm/mmap.c | 12 +++++++-----
> mm/vmscan.c | 11 ++++++-----
> 3 files changed, 23 insertions(+), 16 deletions(-)
>
next prev parent reply other threads:[~2026-09-07 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 18:31 [PATCH v2 0/3] mm: minor janitorial style cleanups Christos Skarlos
2026-09-05 18:31 ` [PATCH v2 1/3] mm/mmap: fix various coding style warnings Christos Skarlos
2026-09-05 18:31 ` [PATCH v2 2/3] mm/vmscan: fix various coding style warnings and errors Christos Skarlos
2026-09-05 18:31 ` [PATCH v2 3/3] mm/hugetlb: fix various coding style warnings Christos Skarlos
2026-09-07 7:43 ` Vlastimil Babka (SUSE) [this message]
2026-09-07 8:58 ` [PATCH v2 0/3] mm: minor janitorial style cleanups Christos Skarlos
2026-09-07 9:10 ` Christos Skarlos
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=60a8cf51-1493-4dbd-8779-8f007f6783a0@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=christosskarlos.kernel@gmail.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=nico.pache@linux.dev \
--cc=osalvador@suse.de \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=usama.arif@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=ziy@nvidia.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 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.