From: Luo Jie <quic_luoj@quicinc.com>
To: Markus Elfring <Markus.Elfring@web.de>, <cocci@inria.fr>,
Catalin Marinas <catalin.marinas@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Julia Lawall <Julia.Lawall@inria.fr>,
Marc Zyngier <maz@kernel.org>,
Nicolas Palix <nicolas.palix@imag.fr>,
Oliver Upton <oliver.upton@linux.dev>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>, Yury Norov <yury.norov@gmail.com>,
Zenghui Yu <yuzenghui@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kvmarm@lists.linux.dev>,
Andrew Lunn <andrew@lunn.ch>,
Kiran Kumar C.S.K <quic_kkumarcs@quicinc.com>,
Lei Wei <quic_leiwei@quicinc.com>,
Pavithra R <quic_pavir@quicinc.com>,
"Suruchi Agarwal" <quic_suruchia@quicinc.com>,
<quic_linchen@quicinc.com>
Subject: Re: [PATCH v6] coccinelle: misc: Add field_modify script
Date: Fri, 27 Jun 2025 12:33:15 +0800 [thread overview]
Message-ID: <a3498578-e3ef-4c63-a132-56ba6ac24900@quicinc.com> (raw)
In-Reply-To: <e52cb86b-01be-4560-a1da-a6b07108d651@web.de>
On 6/26/2025 3:43 PM, Markus Elfring wrote:
>> +coccilib.report.print_report(p[0], "WARNING: Consider using FIELD_MODIFY helper on %s" % (x))
>
> Would you find it a bit nicer to use also another formatted string literal
> as a function call parameter?
> (The recent code adjustment indicated something for the operation mode “org”.)
> https://docs.python.org/3/reference/lexical_analysis.html#f-strings
>
> Regards,
> Markus
Sure, I agree that using a formatted string literal as a function call
parameter will make the code cleaner. I will update the function call
as shown below in the next revision.
coccilib.report.print_report(p[0], f"WARNING: Consider using
FIELD_MODIFY helper on {x}")
prev parent reply other threads:[~2025-06-27 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 6:02 Luo Jie
2025-06-26 7:43 ` Markus Elfring
2025-06-27 4:33 ` Luo Jie [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=a3498578-e3ef-4c63-a132-56ba6ac24900@quicinc.com \
--to=quic_luoj@quicinc.com \
--cc=Julia.Lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=cocci@inria.fr \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maz@kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=oliver.upton@linux.dev \
--cc=quic_kkumarcs@quicinc.com \
--cc=quic_leiwei@quicinc.com \
--cc=quic_linchen@quicinc.com \
--cc=quic_pavir@quicinc.com \
--cc=quic_suruchia@quicinc.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yury.norov@gmail.com \
--cc=yuzenghui@huawei.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®