public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 4/4] scripts/kernel-doc: some fixes to kernel-doc comments
Date: Mon, 12 Jan 2026 14:11:47 +0200	[thread overview]
Message-ID: <228d7af7534816416b574e17624e58285d57ef6f@intel.com> (raw)
In-Reply-To: <de2a70da3c1e3df8ca74196bcc7e44c041ff205b.1768216455.git.mchehab+huawei@kernel.org>

On Mon, 12 Jan 2026, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> There are some typos and English errors at the kernel-doc.py comments.
>
> Locate them with the help of LLM (gpt-oss 14B), locally excecuted
> with this prompt:
>
>     review English grammar andsyntax at the comments on the code
>     below:
>     <cat scripts/kernel-doc.py>
>
> Not all results are flowers, although it caught several minor
> issues there. Add the pertinent fixes, discarding the bad ones.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  scripts/kernel-doc.py | 24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/scripts/kernel-doc.py b/scripts/kernel-doc.py
> index bcb60136fc9c..5086248ee532 100755
> --- a/scripts/kernel-doc.py
> +++ b/scripts/kernel-doc.py
> @@ -9,10 +9,10 @@
>  #       The rationale is that it shall fail gracefully during Kernel
>  #       compilation with older Kernel versions. Due to that:
>  #       - encoding line is needed here;
> -#       - no f-strings can be used on this file.
> -#       - the libraries that require newer versions can only be included
> -#         after Python version is checked.
> -
> +#       - f‑strings cannot be used in this file.
> +#       - libraries that require newer versions can only be included
> +#         after the Python version has been checked.
> +#
>  # Converted from the kernel-doc script originally written in Perl
>  # under GPLv2, copyrighted since 1998 by the following authors:
>  #
> @@ -132,13 +132,13 @@ May be used multiple times.
>  """
>  
>  EXPORT_DESC = """
> -Only output documentation for the symbols that have been
> +Only output documentation for symbols that have been
>  exported using EXPORT_SYMBOL() and related macros in any input
>  FILE or -export-file FILE.
>  """
>  
>  INTERNAL_DESC = """
> -Only output documentation for the symbols that have NOT been
> +Only output documentation for symbols that have NOT been
>  exported using EXPORT_SYMBOL() and related macros in any input
>  FILE or -export-file FILE.
>  """
> @@ -161,7 +161,7 @@ Header and C source files to be parsed.
>  """
>  
>  WARN_CONTENTS_BEFORE_SECTIONS_DESC = """
> -Warns if there are contents before sections (deprecated).
> +Warn if there are contents before sections (deprecated).
>  
>  This option is kept just for backward-compatibility, but it does nothing,
>  neither here nor at the original Perl script.
> @@ -169,7 +169,7 @@ neither here nor at the original Perl script.
>  
>  
>  class MsgFormatter(logging.Formatter):
> -    """Helper class to format warnings on a similar way to kernel-doc.pl"""
> +    """Helper class to format warnings in a similar way to kernel-doc.pl."""
>  
>      def format(self, record):
>          record.levelname = record.levelname.capitalize()
> @@ -268,7 +268,7 @@ def main():
>                          help=NOSYMBOL_DESC)
>  
>      parser.add_argument("-D", "-no-doc-sections", "--no-doc-sections",
> -                        action='store_true', help="Don't outputt DOC sections")
> +                        action='store_true', help="Don't output DOC sections")
>  
>      parser.add_argument("files", metavar="FILE",
>                          nargs="+", help=FILES_DESC)
> @@ -297,12 +297,12 @@ def main():
>      python_ver = sys.version_info[:2]
>      if python_ver < (3,6):
>          #
> -        # Depending on Kernel configuration, kernel-doc --none is called at
> +        # Depending on the Kernel configuration, kernel-doc --none is called at
>          # build time. As we don't want to break compilation due to the
>          # usage of an old Python version, return 0 here.
>          #
>          if args.none:
> -            logger.error("Python 3.6 or later is required by kernel-doc. skipping checks")
> +            logger.error("Python 3.6 or later is required by kernel‑doc. Skipping checks")

Please don't add silly non-breaking space in there.

>              sys.exit(0)
>  
>          sys.exit("Python 3.6 or later is required by kernel-doc. Aborting.")
> @@ -311,7 +311,7 @@ def main():
>          logger.warning("Python 3.7 or later is required for correct results")
>  
>      #
> -    # Import kernel-doc libraries only after checking Python version
> +    # Import kernel-doc libraries only after checking the Python version
>      #
>      from kdoc.kdoc_files import KernelFiles             # pylint: disable=C0415
>      from kdoc.kdoc_output import RestFormat, ManFormat  # pylint: disable=C0415

-- 
Jani Nikula, Intel

      reply	other threads:[~2026-01-12 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 11:23 [PATCH 0/4] kernel-doc: fix -Werror issues Mauro Carvalho Chehab
2026-01-12 11:23 ` [PATCH 1/4] scripts/kernel-doc: fix logic to handle unissued warnings Mauro Carvalho Chehab
2026-01-12 11:43   ` Andy Shevchenko
2026-01-12 11:23 ` [PATCH 2/4] scripts/kernel-doc: avoid error_count overflows Mauro Carvalho Chehab
2026-01-12 12:02   ` Jani Nikula
2026-01-12 14:39     ` Mauro Carvalho Chehab
2026-01-12 11:23 ` [PATCH 3/4] scripts/kernel-doc: ensure that comments are using our coding style Mauro Carvalho Chehab
2026-01-12 11:23 ` [PATCH 4/4] scripts/kernel-doc: some fixes to kernel-doc comments Mauro Carvalho Chehab
2026-01-12 12:11   ` Jani Nikula [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=228d7af7534816416b574e17624e58285d57ef6f@intel.com \
    --to=jani.nikula@intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.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