From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Matthew Wilcox <willy@infradead.org>,
Manish Kumar <manish1588@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: fix VM_WARN_ONCE indentation in page_alloc.c
Date: Thu, 15 Jan 2026 22:34:25 +0100 [thread overview]
Message-ID: <32c86644-d1b1-46a7-89a6-da5e99ba21c6@kernel.org> (raw)
In-Reply-To: <aWlMp50lLH8xhx-Z@casper.infradead.org>
On 1/15/26 21:23, Matthew Wilcox wrote:
> On Fri, Jan 16, 2026 at 01:43:05AM +0530, Manish Kumar wrote:
>> Signed-off-by: Manish Kumar <manish1588@gmail.com>
>
> Stop it.
>
Manish, these tiny cleanup patches that don't add any real value just
consume reviewer and maintainer load.
Flooding the list with them is frowned upon ;)
--
Cheers
David
prev parent reply other threads:[~2026-01-15 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:13 Manish Kumar
2026-01-15 20:23 ` Matthew Wilcox
2026-01-15 21:34 ` David Hildenbrand (Red Hat) [this message]
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=32c86644-d1b1-46a7-89a6-da5e99ba21c6@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manish1588@gmail.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox