From: "Zi Yan" <ziy@nvidia.com>
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: <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>, <vbabka@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 2/3] mm/vamscan: fix various coding style warnings and errors
Date: Sat, 05 Sep 2026 12:22:18 -0400 [thread overview]
Message-ID: <DL7IRL92BVCW.33O9J7W8PQJL8@nvidia.com> (raw)
In-Reply-To: <20260905140140.60792-4-christosskarlos.kernel@gmail.com>
On Sat Sep 5, 2026 at 10:01 AM EDT, Christos Skarlos wrote:
> Resolve coding style issues flagged by checkpatch.pl script. Specifically:
> - Add missing blank lines after variable declarations.
> - Replace "unsigned" with "unsigned int".
> - Replace spaces with tabs where possible.
>
> No functional changes are introduced.
>
> Signed-off-by: Christos Skarlos <christosskarlos.kernel@gmail.com>
> ---
> mm/vmscan.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
Your subject has a typo: s/vamscan/vmscan
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index f11491ee9ed5..8637cc0910fa 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -535,7 +535,7 @@ void reclaim_throttle(pg_data_t *pgdat, enum vmscan_throttle_state reason)
> * writeback to a slow device to excessive referenced folios at the tail
> * of the inactive LRU.
> */
> - switch(reason) {
> + switch (reason) {
> case VMSCAN_THROTTLE_WRITEBACK:
> timeout = HZ/10;
>
> @@ -1529,6 +1529,7 @@ static unsigned int shrink_folio_list(struct list_head *folio_list,
> VM_BUG_ON_FOLIO(folio_test_active(folio), folio);
> if (!folio_test_mlocked(folio)) {
> int type = folio_is_file_lru(folio);
> +
> folio_set_active(folio);
> stat->nr_activate[type] += nr_pages;
> count_memcg_folio_events(folio, PGACTIVATE, nr_pages);
> @@ -2073,8 +2074,8 @@ static void shrink_active_list(unsigned long nr_to_scan,
> LIST_HEAD(l_hold); /* The folios which were snipped off */
> LIST_HEAD(l_active);
> LIST_HEAD(l_inactive);
> - unsigned nr_deactivate, nr_activate;
> - unsigned nr_rotated = 0;
> + unsigned int nr_deactivate, nr_activate;
> + unsigned int nr_rotated = 0;
> bool file = is_file_lru(lru);
> struct pglist_data *pgdat = lruvec_pgdat(lruvec);
>
> @@ -2614,7 +2615,7 @@ static void get_scan_count(struct lruvec *lruvec, struct scan_control *sc,
> /*
> * If there is enough inactive page cache, we do not reclaim
> * anything from the anonymous working right now to make sure
> - * a streaming file access pattern doesn't cause swapping.
> + * a streaming file access pattern doesn't cause swapping.
> */
> if (sc->cache_trim_mode) {
> scan_balance = SCAN_FILE;
> @@ -3416,6 +3417,7 @@ static bool get_next_vma(unsigned long mask, unsigned long size, struct mm_walk
> {
> unsigned long start = round_up(*vm_end, size);
> unsigned long end = (start | ~mask) + 1;
> +
> VMA_ITERATOR(vmi, args->mm, start);
Like I said in patch 1, no new line is needed here.
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-09-05 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 14:01 [PATCH 0/3] mm: minor janitorial style cleanups Christos Skarlos
2026-09-05 14:01 ` [PATCH] mm/huge_memory: fix various coding style warnings Christos Skarlos
2026-09-05 16:07 ` Zi Yan
2026-09-05 14:01 ` [PATCH 1/3] mm/mmap: " Christos Skarlos
2026-09-05 16:19 ` Zi Yan
2026-09-05 14:01 ` [PATCH 2/3] mm/vamscan: fix various coding style warnings and errors Christos Skarlos
2026-09-05 16:22 ` Zi Yan [this message]
2026-09-05 14:01 ` [PATCH 3/3] mm/hugetlb: fix various coding style warnings Christos Skarlos
2026-09-05 16:24 ` Zi Yan
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=DL7IRL92BVCW.33O9J7W8PQJL8@nvidia.com \
--to=ziy@nvidia.com \
--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=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.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