Linux Documentation
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: ryszard.knop@intel.com
Cc: intel-xe@lists.freedesktop.org, jani.nikula@linux.intel.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org, shuicheng.lin@intel.com, corbet@lwn.net
Subject: Re: [PATCH v3] scripts/kernel-doc: Suggest possible names for excess descriptions
Date: Fri, 31 Jul 2026 12:19:41 +0900	[thread overview]
Message-ID: <22a9276d-c103-4306-a617-7f34abcd5c29@gmail.com> (raw)
In-Reply-To: <20260717125753.634550-1-ryszard.knop@intel.com>

Hi,

Daily linux-next documentation build at https://www.kernel.org/doc/html/next/
has stopped working since July 23.

In my bisection using a debian bookworm container (python 3.11.2 +
sphinx 5.3.0), this patch, which is now commit d7758384ccb4
("scripts/kernel-doc: Suggest possible names for excess descriptions"),
is blamed as the first bad commit.  Reverting it resolves the build
error.

Error message from "make htmldocs" looks like this:

--------------------------------------------------------
Exception occurred:
  File "/linux/tools/lib/python/kdoc/kdoc_files.py", line 16, in <module>
    from kdoc.kdoc_parser import KernelDoc
  File "/linux/tools/lib/python/kdoc/kdoc_parser.py", line 604
    return f"(did you mean one of: '{"', '".join(suggestions)}')"
                                                                 ^
SyntaxError: f-string: expecting '}'
--------------------------------------------------------

I think this needs python3 3.12 or better.

Can you make this script compatible with python3 3.9, which is the
minimal version listed in Documentation/process/changes.rst?

Thanks, Akira

      parent reply	other threads:[~2026-07-31  3:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 11:12 [PATCH] scripts/kernel-doc: Suggest possible names for excess descriptions Ryszard Knop
2026-07-14 21:44 ` Randy Dunlap
2026-07-15 11:18   ` Knop, Ryszard
2026-07-15 11:17 ` [PATCH v2] " Ryszard Knop
2026-07-15 12:42   ` Mauro Carvalho Chehab
2026-07-15 13:21     ` Knop, Ryszard
2026-07-15 13:52       ` Mauro Carvalho Chehab
2026-07-17 13:17         ` Knop, Ryszard
2026-07-16 22:40 ` [PATCH] " Jonathan Corbet
2026-07-17 13:07   ` Knop, Ryszard
2026-07-17 12:57 ` [PATCH v3] " Ryszard Knop
2026-07-17 16:28   ` Randy Dunlap
2026-07-22 16:15   ` Jonathan Corbet
2026-07-31  3:19   ` Akira Yokosawa [this message]

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=22a9276d-c103-4306-a617-7f34abcd5c29@gmail.com \
    --to=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=ryszard.knop@intel.com \
    --cc=shuicheng.lin@intel.com \
    /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