Re: [PATCH 0/1] docs: examples of pages affected by heading overflow
From: Randy Dunlap
Date: Sat Mar 21 2026 - 17:31:52 EST
On 3/21/26 7:48 AM, Rito Rhymes wrote:
> Examples of affected pages on docs.kernel.org this patch improves:
> userspace-api/gpio/gpio-handle-set-line-values-ioctl.html
> userspace-api/gpio/gpio-v2-get-lineinfo-watch-ioctl.html
> userspace-api/gpio/gpio-handle-get-line-values-ioctl.html
> userspace-api/gpio/gpio-get-lineinfo-unwatch-ioctl.html
> userspace-api/gpio/gpio-v2-lineinfo-changed-read.html
> userspace-api/gpio/gpio-get-lineinfo-watch-ioctl.html
> userspace-api/gpio/gpio-v2-line-set-config-ioctl.html
> userspace-api/gpio/gpio-v2-line-get-values-ioctl.html
> userspace-api/sysfs-platform_profile.html
>
> Rito Rhymes (1):
> docs: allow long unbroken headings to wrap and prevent overflow
>
> Documentation/sphinx-static/custom.css | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Some of these (html pages listed above) now split the heading where it
might appear that a split is not needed. Maybe the heading was going past
the "right margin" previously and after the patch it does not do that?
E.g., before the patch I see this heading:
GPIO_V2_LINE_GET_VALUES_IOCTL
After the patch I see:
GPIO_V2_LINE_GET_VALUES_IOCT
L
Regarding the last example that has a problem, that heading just needs
to be fixed. The "(e.g. ...)" part of it shouldn't be in the heading.
To me these 4 patches:
[PATCH 1/1] docs: allow inline literals in paragraphs to wrap to prevent overflow
[PATCH 1/1] docs: allow long unbroken headings to wrap and prevent overflow
[PATCH 1/1] docs: contain horizontal overflow in C API descriptions
[PATCH 1/1] docs: wrap generated tables to contain small-screen overflow
feel inconsistent. In some cases they add horizontal scrolling while in
other cases they add auto-wrapping.
Maybe it's just me, but you might need some more justification for making
the choices in the patches.
However, prior to these patches there was definitely some loss of
characters on the right side, e.g., in C API blocks.
thanks.
--
~Randy