From: Jonathan Corbet <corbet@lwn.net>
To: Nick Huang <sef1548@gmail.com>, Lorenzo Stoakes <ljs@kernel.org>
Cc: "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>,
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>,
Mike Rapoport <rppt@kernel.org>,
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 00:43:03 -0600 [thread overview]
Message-ID: <87jyu2w2rs.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CABZAGRHXtjzGJrgR1NAmVHFMP9eL5zZr3DaTAtAvywv_1sOHdw@mail.gmail.com>
Nick Huang <sef1548@gmail.com> writes:
> 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.
>
> 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 be respectful, start by reading what has been sent to
you; the problems with your submission were well explained, more than
once.
To reiterate:
- Do not send LLM-generated material without marking it as such as
described in our developer documentation.
- Do not attempt to document systems that you do not, yourself,
understand; you have no hope of getting it right, and you will only
succeed in wasting the time of the people who have to review your
changes.
The point of documentation is to be informative, accurate, and useful;
simply filling in a bunch of words is not helpful to anybody.
Thanks,
jon
next prev parent reply other threads:[~2026-04-20 6:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 0:06 [PATCH] docs: Add overview and SLUB allocator sections to slab documentation 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
2026-04-20 6:43 ` Jonathan Corbet [this message]
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=87jyu2w2rs.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--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=sef1548@gmail.com \
--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