From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/vmalloc: read vm_map_ram block regions from the requested offset
Date: Mon, 19 Oct 2026 13:48:46 +0100 [thread overview]
Message-ID: <atYRUyFHca-giQcw@gremlin> (raw)
In-Reply-To: <atSM69faDNgmLNVJ@milan>
-cc slopper.
Keep in mind that this individual is flooding the kernel with slop.
We should be wary about encouraging this kind of behaviour. I suggest taking
over patches, 'discussion' will likely result in having to deal with a meat
proxy.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-19 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 15:41 [PATCH v1] " Nickolai Zeldovich
2026-10-17 19:52 ` Andrew Morton
2026-10-17 23:13 ` [PATCH v2] " Nickolai Zeldovich
2026-10-18 9:10 ` Uladzislau Rezki
2026-10-19 12:48 ` Lorenzo Stoakes (ARM) [this message]
2026-10-17 23:14 ` [PATCH v1] " Nickolai Zeldovich
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=atYRUyFHca-giQcw@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.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
all inboxes | Powered by JetHome®