From: Nick Huang <sef1548@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>, Harry Yoo <harry@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>, Hao Li <hao.li@linux.dev>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Add overview and SLUB allocator sections to slab documentation
Date: Mon, 20 Apr 2026 18:41:05 +0800 [thread overview]
Message-ID: <CABZAGRGx+7Wbw1G+sjB9cdR-9C6PdT3OAWPMd=UC=5WHrnvV1Q@mail.gmail.com> (raw)
In-Reply-To: <aeXK4tjGFUgKDf5-@kernel.org>
Mike Rapoport <rppt@kernel.org> 於 2026年4月20日週一 下午2:42寫道:
>
> Hi Nick,
>
> On Mon, Apr 20, 2026 at 12:52:25PM +0800, Nick Huang wrote:
> >
> > I am really sorry for causing trouble for everyone. I would like to
> > ask which aspect of mine was disrespectful, so that I can be more
> > careful next time.
>
> Maintainers time is valuable and sending LLM generated patch completely
> without understanding what it is about is disrespect for maintainers wasted
> time.
>
> > If I want to make this kind of change, should I send an [RFC patch] to
> > ask for everyone's opinion?
>
> If you want to make that kind of change, you should start with researching
> and understanding yourself what the code is doing, double check the LLM
> output and verify it and not just take an LLM slop and send it.
>
> > Sorry, I really am not very clear about the process.
>
> Start with reading kernel process documentation:
> https://docs.kernel.org/process/development-process.html
>
> > --
> > Regards,
> > Nick Huang
>
> --
> Sincerely yours,
> Mike.
Thank you for your suggestion. I will read the kernel process
documentation carefully.
--
Regards,
Nick Huang
next prev parent reply other threads:[~2026-04-20 10:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 0:06 Nick Huang
2026-04-18 5:04 ` Matthew Wilcox
2026-04-18 5:27 ` Nick Huang
2026-04-18 6:12 ` Nick Huang
2026-04-18 9:11 ` Lorenzo Stoakes
2026-04-18 11:00 ` Nick Huang
2026-04-18 11:20 ` Vlastimil Babka (SUSE)
2026-04-18 15:30 ` Harry Yoo (Oracle)
2026-04-18 6:19 ` Harry Yoo (Oracle)
2026-04-18 9:07 ` Lorenzo Stoakes
2026-04-18 16:15 ` Matthew Wilcox
2026-04-19 8:35 ` David Hildenbrand (Arm)
2026-04-19 13:17 ` Lorenzo Stoakes
2026-04-20 4:52 ` Nick Huang
2026-04-20 6:42 ` Mike Rapoport
2026-04-20 10:41 ` Nick Huang [this message]
2026-04-20 6:43 ` Jonathan Corbet
2026-04-20 10:43 ` Nick Huang
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='CABZAGRGx+7Wbw1G+sjB9cdR-9C6PdT3OAWPMd=UC=5WHrnvV1Q@mail.gmail.com' \
--to=sef1548@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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