mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: [PATCH v2 01/15] docs: custom.css: prevent li marker to override text
Date: Thu, 15 Jan 2026 16:40:22 +0100	[thread overview]
Message-ID: <f139d304fe4dab288152caf1fda921bd8d9dd7d5.1768488832.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1768488832.git.mchehab+huawei@kernel.org>

There's currently an issue with li marker: it is set to use
-1em, which actually makes it override the text. This is visible
on indexes that are deep enough.

Fix it.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/sphinx-static/custom.css | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/sphinx-static/custom.css b/Documentation/sphinx-static/custom.css
index 06cedbae095c..b6a7a5f6b6d4 100644
--- a/Documentation/sphinx-static/custom.css
+++ b/Documentation/sphinx-static/custom.css
@@ -30,6 +30,9 @@ img.logo {
     margin-bottom: 20px;
 }
 
+/* The default is to use -1em, wich makes it override text */
+li { text-indent: 0em; }
+
 /*
  * Parameters for the display of function prototypes and such included
  * from C source files.
-- 
2.52.0


  reply	other threads:[~2026-01-15 15:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 15:40 [PATCH v2 00/15] Add kernel-doc modules to Documentation/tools Mauro Carvalho Chehab
2026-01-15 15:40 ` Mauro Carvalho Chehab [this message]
2026-01-15 15:40 ` [PATCH v2 02/15] docs: conf.py: don't use doctree with a different meaning Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 03/15] docs: conf: don't rely on cwd to get documentation location Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 04/15] docs: enable Sphinx autodoc extension to allow documenting python Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 05/15] docs: custom.css: add CSS for python Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 06/15] docs: kdoc: latex_fonts: Improve docstrings and comments Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 07/15] docs: kdoc_files: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 08/15] docs: kdoc_item: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 09/15] docs: kdoc_parser: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 10/15] docs: kdoc_output: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 11/15] docs: kdoc_re: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 12/15] docs: kdoc: parse_data_structs: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 13/15] docs: kdoc: enrich_formatter: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 14/15] docs: kdoc: python_version: " Mauro Carvalho Chehab
2026-01-15 15:40 ` [PATCH v2 15/15] docs: add kernel-doc modules documentation Mauro Carvalho Chehab

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=f139d304fe4dab288152caf1fda921bd8d9dd7d5.1768488832.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nfraprado@collabora.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

all inboxes | Powered by JetHome®