From: Pratyush Yadav <pratyush@kernel.org>
To: Haolong Wang <18766350203@163.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] mm/memfd_luo: preserve the sealed exec-bit state; reject kernel-private shmem files
Date: Wed, 14 Oct 2026 11:43:13 +0200 [thread overview]
Message-ID: <2vxzmrsgipn2.fsf@kernel.org> (raw)
In-Reply-To: <20261014035228.473825-1-18766350203@163.com> (Haolong Wang's message of "Wed, 14 Oct 2026 11:52:25 +0800")
Hi,
I refuse to review this series. It looks entirely LLM generated with no
quality controls at all. LLM generated content is fine, but you can't
just post low quality patches and expect humans to spend time reviewing
them.
The commit messages are unreadable LLM ramblings, the code is all over
the place and makes very little sense, you have made 3 versions in the
same day, your cover letter doesn't even explain your use case and why
you make this change, and so on.
Future postings with similar quality will also be ignored.
Please spend time to understand the kernel development process and spend
_your own_ time understanding your code and polishing it.
[...]
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-10-14 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 3:52 [PATCH v3 0/3] mm/memfd_luo: preserve the sealed exec-bit state; reject kernel-private shmem files Haolong Wang
2026-10-14 3:52 ` [PATCH v3 1/3] mm/memfd_luo: " Haolong Wang
2026-10-14 3:52 ` [PATCH v3 2/3] mm/memfd_luo: carry the sealed exec-bit state in the preserved record Haolong Wang
2026-10-14 3:52 ` [PATCH v3 3/3] mm/memfd_luo: release preserved folios when retrieve fails Haolong Wang
2026-10-14 9:43 ` Pratyush Yadav [this message]
2026-10-14 10:01 ` [PATCH v3 0/3] mm/memfd_luo: preserve the sealed exec-bit state; reject kernel-private shmem files Haolong Wang
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=2vxzmrsgipn2.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=18766350203@163.com \
--cc=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.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 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.