mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Ricardo Ungerer <ungerer.ricardo@gmail.com>,
	linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Ricardo Ungerer <ungerer.ricardo@gmail.com>
Subject: Re: [PATCH v2] jobserver: Fix typo in docstring
Date: Tue, 17 Mar 2026 08:44:40 -0600	[thread overview]
Message-ID: <871phiecrr.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260316220218.568022-1-ungerer.ricardo@gmail.com>

Ricardo Ungerer <ungerer.ricardo@gmail.com> writes:

> This commit fixes small typos in the docstring of jobserver.py.

For future reference, our guidance says to avoid "this commit", and some
maintainers are pretty firm about that.

> Signed-off-by: Ricardo Ungerer <ungerer.ricardo@gmail.com>
> ---
> Changes in v2:
> - Fix a Sphynx regression created by v1 when removed the second colon.
> ---
>  tools/lib/python/jobserver.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/lib/python/jobserver.py b/tools/lib/python/jobserver.py
> index aba22c33393d..0b1ffdf9f7a3 100755
> --- a/tools/lib/python/jobserver.py
> +++ b/tools/lib/python/jobserver.py
> @@ -8,14 +8,14 @@
>  """
>  Interacts with the POSIX jobserver during the Kernel build time.
>  
> -A "normal" jobserver task, like the one initiated by a make subrocess would do:
> +A "normal" jobserver task, like the one initiated by a make subprocess would do:
>  
>      - open read/write file descriptors to communicate with the job server;
>      - ask for one slot by calling::
>  
>          claim = os.read(reader, 1)
>  
> -    - when the job finshes, call::
> +    - when the job finishes, call::
>  

Applied, thanks.

jon

      reply	other threads:[~2026-03-17 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 22:02 Ricardo Ungerer
2026-03-17 14:44 ` Jonathan Corbet [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=871phiecrr.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=ungerer.ricardo@gmail.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

all inboxes | Powered by JetHome®