public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Rito Rhymes <rito@ritovision.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Rito Rhymes <rito@ritovision.com>
Subject: [PATCH 0/2] docs: contain overflow from long links
Date: Sat, 21 Mar 2026 14:08:39 -0400	[thread overview]
Message-ID: <20260321180841.10166-1-rito@ritovision.com> (raw)

Patch 1 allows long link text to wrap per character so unbroken links
in the main document body do not force page-wide horizontal scroll
overflow.

Patch 2 remains necessary for rendered reference links inside docutils
tables, where the affected table case still needs an explicit selector
to keep the table within the content column.

Some of these pages may also overflow for other reasons, but the
examples listed under [2/2] specifically include tables containing
long reference links that may still need a table-specific CSS rule
to keep the table within the content column.


Examples of affected pages on docs.kernel.org this patch improves:

[1/2]
  firmware-guide/acpi/non-d0-probe.html
  firmware-guide/acpi/lpit.html
  arch/arm/vlocks.html
  arch/arm/keystone/overview.html
  arch/arm/keystone/knav-qmss.html
  arch/loongarch/introduction.html
  arch/nios2/nios2.html
  arch/x86/earlyprintk.html
  arch/x86/orc-unwinder.html#etymology
  arch/x86/tdx.html
  arch/x86/sva.html
  driver-api/xilinx/eemi.html

[2/2]
  arch/openrisc/openrisc_port.html
  power/apm-acpi.html
  networking/devlink/stmmac.html
  filesystems/ext2.html
  networking/l2tp.html
  process/embargoed-hardware-issues.html
  arch/x86/boot.html
  networking/devlink/devlink-info.html
  admin-guide/sysctl/fs.html
  userspace-api/ioctl/ioctl-number.html

Rito Rhymes (2):
  docs: allow long links to wrap per character to prevent page overflow
  docs: allow long table reference links to wrap and prevent overflow

 Documentation/sphinx-static/custom.css | 10 ++++++++++
 1 file changed, 10 insertions(+)

-- 
2.51.0

             reply	other threads:[~2026-03-21 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 18:08 Rito Rhymes [this message]
2026-03-21 18:08 ` [PATCH 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-21 18:08 ` [PATCH 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
2026-03-22 19:20 ` [PATCH v2 0/2] docs: contain overflow from long links Rito Rhymes
2026-03-22 19:20   ` [PATCH v2 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-22 19:20   ` [PATCH v2 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
2026-03-23 15:24 ` [PATCH v3 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-23 15:24   ` [PATCH v3 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
2026-03-25  0:50     ` Randy Dunlap
2026-03-25  0:50   ` [PATCH v3 1/2] docs: allow long links to wrap per character to prevent page overflow Randy Dunlap
2026-03-25 19:15   ` Jonathan Corbet

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=20260321180841.10166-1-rito@ritovision.com \
    --to=rito@ritovision.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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