From: Jonathan Corbet <corbet@lwn.net>
To: Rito Rhymes <rito@ritovision.com>, linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Rito Rhymes <rito@ritovision.com>
Subject: Re: [PATCH v2 0/1] docs: examples of pages affected by C API signature overflow
Date: Sun, 22 Mar 2026 14:35:21 -0600 [thread overview]
Message-ID: <874im7eh6e.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260322193740.68784-1-rito@ritovision.com>
Rito Rhymes <rito@ritovision.com> writes:
> Examples of affected pages on docs.kernel.org this patch improves:
> core-api/genalloc.html
> userspace-api/iommufd.html
> userspace-api/liveupdate.html
> core-api/liveupdate.html
> arch/sh/index.html
> arch/x86/sgx.html
> devicetree/kernel-api.html
> userspace-api/fwctl/fwctl-cxl.html
> driver-api/regulator.html
> driver-api/reset.html
> driver-api/s390-drivers.html
> driver-api/scsi.html
> driver-api/spi.html
> driver-api/target.html
> driver-api/wbrf.html
> driver-api/wmi.html
>
> Rito Rhymes (1):
> docs: contain horizontal overflow in C API descriptions
>
> Documentation/sphinx-static/custom.css | 7 +++++++
> 1 file changed, 7 insertions(+)
This is a general comment applying to most of the patches you have sent:
is not a typical or particularly helpful cover letter. The cover letter
tells reviewers what the series as a whole does; this one does not.
Perhaps more to the point, a cover letter is rarely warranted for a
single patch; just put any relevant information into the changelog of
the patch itself.
In this case, some examples of the problem being solved are certainly
warranted, though perhaps not so many as given here. They should be in
the patch changelog so that somebody wondering, years from now, why the
patch was applied can gain that understanding.
The names of HTML files are perhaps not ideal; since you're talking
about docs.kernel.org in particular, you could give URLs that people
could view directly. So, for example:
https://docs.kernel.org/6.19/core-api/genalloc.html
Note the explicit version so that the problem will be findable in the
distant future, even after the fix is applied.
Thanks,
jon
next prev parent reply other threads:[~2026-03-22 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 14:25 [PATCH 0/1] docs: examples of pages affected by C API signature overflow Rito Rhymes
2026-03-21 14:25 ` [PATCH 1/1] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-21 21:12 ` Randy Dunlap
2026-03-22 19:37 ` [PATCH v2 0/1] docs: examples of pages affected by C API signature overflow Rito Rhymes
2026-03-22 19:37 ` [PATCH v2 1/1] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-22 20:35 ` Jonathan Corbet [this message]
2026-03-23 9:57 ` [PATCH v2 0/1] docs: examples of pages affected by C API signature overflow Rito Rhymes
2026-03-23 13:42 ` Jonathan Corbet
2026-03-23 15:33 ` [PATCH v3] docs: contain horizontal overflow in C API descriptions Rito Rhymes
2026-03-25 19:00 ` Jonathan Corbet
2026-03-25 20:50 ` Rito Rhymes
2026-03-25 21:14 ` Jonathan Corbet
2026-03-26 19:10 ` Rito Rhymes
2026-03-26 18:43 ` [PATCH v4] docs: wrap long C API signatures to prevent page overflow Rito Rhymes
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=874im7eh6e.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rito@ritovision.com \
--cc=skhan@linuxfoundation.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