From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Farber, Eliav" <farbere@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] mm: add vmf_insert_pfn_order() and vmf_pfn_order_ok() helpers
Date: Sun, 15 Nov 2026 17:54:54 +0100 [thread overview]
Message-ID: <042795ab-e8af-443f-b34c-72c674c0ea32@kernel.org> (raw)
In-Reply-To: <BY3PR18MB4722713137ADE7A59A1EB81BC67D2@BY3PR18MB4722.namprd18.prod.outlook.com>
On 11/15/26 07:44, Farber, Eliav wrote:
> On 11/13/26 11:39, David Hildenbrand (Arm) wrote:
>> On 11/12/26 16:55, Farber, Eliav wrote:
>>> We crossed in flight: v2 went out about six minutes before your mail, so
>>> you were reading v1. I posted it to address sashiko-bot's review of v1,
>>
>> First, wait for human review. Always.
>>
>> Second, read Documentation/process/submitting-patches.rst
>>
>> "Wait for a minimum of one week before resubmitting or pinging reviewers
>> - possibly longer during busy times like merge windows."
>>
>> Because we have much other priorities right now :)
>
> Understood, sorry about that. I won't post a new version before I get
> human review, and not before a week has passed.
>
>> Before I reply to anything in here: did an LLM compose most of these walls of
>> text? :)
>
> Yes, partly. I used an LLM while working on this series, to help with
> the code and to find bugs, mostly for testing. I also used it to write
> the text, and that is why my replies came out so long. I should have
> kept them short, sorry.
I don't want to be angry on a Sunday (I'm not the type of poison), but this
grinds my gears. Your commit description is schloppy, your code is schloppy, and
-- even worse -- your replies are schloppy.
I'm not interested in getting work-schlopped by people that believe their time
is more valuable than mine by feeding me AI schlop on the mailing list.
Please rewrite your answer in a way that doesn't make me hate kernel development.
--
Cheers,
David
next prev parent reply other threads:[~2026-11-15 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:30 [PATCH 0/4] mm, uio: huge PFN mappings for /dev/mem and UIO Eliav Farber
2026-11-11 11:30 ` [PATCH 1/4] mm: add MMAP_PFN_TRACK action and pfn_range_track() for lazy PFN maps Eliav Farber
2026-11-11 11:30 ` [PATCH 2/4] mm: add vmf_insert_pfn_order() and vmf_pfn_order_ok() helpers Eliav Farber
2026-11-11 22:50 ` sashiko-bot
2026-11-12 12:53 ` Farber, Eliav
2026-11-12 13:02 ` David Hildenbrand (Arm)
2026-11-12 15:55 ` Farber, Eliav
2026-11-13 10:39 ` David Hildenbrand (Arm)
2026-11-15 6:44 ` Farber, Eliav
2026-11-15 16:54 ` David Hildenbrand (Arm) [this message]
2026-11-11 11:30 ` [PATCH 3/4] mm/char-mem: implement huge_fault support for /dev/mem Eliav Farber
2026-11-11 22:50 ` sashiko-bot
2026-11-12 12:54 ` Farber, Eliav
2026-11-11 11:30 ` [PATCH 4/4] uio: implement huge_fault support for physical mappings Eliav Farber
2026-11-11 22:50 ` sashiko-bot
2026-11-12 12:54 ` Farber, Eliav
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=042795ab-e8af-443f-b34c-72c674c0ea32@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=farbere@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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.