From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Nickolai Zeldovich <nickolai@csail.mit.edu>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xarray: clear the new head's parent before freeing the old head
Date: Thu, 29 Oct 2026 15:03:05 +0000 [thread overview]
Message-ID: <auNdNjH4zo7OYbe-@gremlin> (raw)
In-Reply-To: <20261027192014.844878-1-nickolai@csail.mit.edu>
Nickolai,
It's pretty 101, but please don't send new revisions in-reply-to older
revisions or feedback [0]. Also, if somebody replies to
you, reply back. You, not your LLM.
Also, you are flooding the kernel with patches, 5 series across 5
subsystems over 2 hrs:
https://lore.kernel.org/all/?q=f%3Anickolai%40csail.mit.edu
I already asked you once to stop doing this [1]. You've carried on.
This is not how to engage with the community. Please contact maintainers
ahead of time and ask 'do you mind if I spam you with slop?'.
Only if they say yes, carry on. Yes we want bug reports. No we don't want
people like you running scripts without permission and sending out dozens
of patches all over the place.
I'm sure you're acting in good faith, so can I please ask you to engage
with maintainers instead of ignoring us and treating our time as valueless?
Thanks.
--
Cheers, Lorenzo
[0]:https://docs.kernel.org/process/submitting-patches.html#explicit-in-reply-to-headers
[1]:https://lore.kernel.org/all/atYQW_lfJdRZnU_n@gremlin/
next prev parent reply other threads:[~2026-10-29 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 20:25 [PATCH v1] xarray: clear the new head's parent before freeing the old head Nickolai Zeldovich
2026-10-23 14:45 ` Matthew Wilcox
2026-10-27 19:20 ` [PATCH v2] " Nickolai Zeldovich
2026-10-29 15:03 ` Lorenzo Stoakes (ARM) [this message]
2026-10-29 15:50 ` Nickolai Zeldovich
2026-10-29 16:04 ` Lorenzo Stoakes (ARM)
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=auNdNjH4zo7OYbe-@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickolai@csail.mit.edu \
--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