From: Jonathan Corbet <corbet@lwn.net>
To: LIU Haoyang <tttturtleruss@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>
Cc: LIU Haoyang <tttturtleruss@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/docs/checktransupdate.py: fix missing prefix in f-string
Date: Sun, 22 Mar 2026 14:55:43 -0600 [thread overview]
Message-ID: <87a4vzd1o0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260308104135.9037-1-tttturtleruss@gmail.com>
LIU Haoyang <tttturtleruss@gmail.com> writes:
> Add a f prefix to f-string in checktransupdate.py.
>
> Fixes: 63e96ce050e5 ("scripts: fix all issues reported by pylint")
> Signed-off-by: LIU Haoyang <tttturtleruss@gmail.com>
> ---
> tools/docs/checktransupdate.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/docs/checktransupdate.py b/tools/docs/checktransupdate.py
> index e894652369a5..bf735562aeeb 100755
> --- a/tools/docs/checktransupdate.py
> +++ b/tools/docs/checktransupdate.py
> @@ -131,7 +131,7 @@ def check_per_file(file_path):
> opath = get_origin_path(file_path)
>
> if not os.path.isfile(opath):
> - logging.error("Cannot find the origin path for {file_path}")
> + logging.error(f"Cannot find the origin path for {file_path}")
> return
Applied, thanks.
jon
prev parent reply other threads:[~2026-03-22 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 10:41 [PATCH] tools/docs/checktransupdate.py: fix missing prefix in f-string LIU Haoyang
2026-03-09 3:50 ` Dongliang Mu
2026-03-09 7:47 ` [PATCH v2] tools/docs/checktransupdate.py: fix all issues reported by pylint Haoyang LIU
2026-03-09 15:54 ` Jonathan Corbet
2026-03-09 16:56 ` Haoyang Liu
2026-03-09 17:42 ` 刘浩阳
2026-03-22 20:55 ` 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=87a4vzd1o0.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tttturtleruss@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