From: Dongliang Mu <dzm91@hust.edu.cn>
To: Jonathan Corbet <corbet@lwn.net>,
Haoyang LIU <tttturtleruss@gmail.com>,
Yanteng Si <si.yanteng@linux.dev>
Cc: hust-os-kernel-patches@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/checktransupdate.py: fix missing f prefix in f-string
Date: Tue, 12 Aug 2025 13:08:12 +0800 [thread overview]
Message-ID: <a32e1a36-8978-45c4-be0c-39e7ccd8f877@hust.edu.cn> (raw)
In-Reply-To: <87qzxhdb65.fsf@trenco.lwn.net>
On 8/12/25 1:24 AM, Jonathan Corbet wrote:
> Haoyang LIU <tttturtleruss@gmail.com> writes:
>
>> add a f prefix for f-string
>>
>> Fixes: 63e96ce050e5 ("scripts: fix all issues reported by pylint")
>> Signed-off-by: Haoyang LIU <tttturtleruss@gmail.com>
>> ---
>> scripts/checktransupdate.py | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/scripts/checktransupdate.py b/scripts/checktransupdate.py
>> index e39529e46c3d..b57fb9139f5f 100755
>> --- a/scripts/checktransupdate.py
>> +++ b/scripts/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
> Ouch, good catch; I've applied this.
Wonder why pylint cannot catch this issue.
The Fixes tag is my commit - "fix all issues reported by pylint", :\
Dongliang Mu
>
> Thanks,
>
> jon
prev parent reply other threads:[~2025-08-12 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 17:07 Haoyang LIU
2025-08-11 17:24 ` Jonathan Corbet
2025-08-12 5:08 ` Dongliang Mu [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=a32e1a36-8978-45c4-be0c-39e7ccd8f877@hust.edu.cn \
--to=dzm91@hust.edu.cn \
--cc=corbet@lwn.net \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--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
all inboxes | Powered by JetHome®