From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Palix <nicolas.palix@imag.fr>,
"cocci@inria.fr" <cocci@inria.fr>
Subject: Re: [PATCH v2] coccinelle: device_attr_show: Adapt to the latest Documentation/filesystems/sysfs.rst
Date: Mon, 22 Jan 2024 03:29:01 +0000 [thread overview]
Message-ID: <d14443fd-96ee-4d94-a149-d81990f64de6@fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2401202217550.3267@hadrien>
On 21/01/2024 05:20, Julia Lawall wrote:
>> V2:
>> - changed title from coccinelle: device_attr_show.cocci: update description and warning message
>> - Fix MODE=patch
>> - Extract patch from the patch set[1] so that maintainer can accept it separately.
> Applied.
>
> I subsequently simplified the patch case to contain the following:
>
> - snprintf(BUF, SZ, FORMAT
> + sysfs_emit(BUF, FORMAT
> ,...);
Great, that was what i want. But i didn't get the correct syntax. I wrote it wrongly:
- snprintf(BUF, SZ, FORMAT, ...);
+ sysfs_emit(BUF, SZ, FORMAT, ...);
>
> This also works for the case where there are only three arguments.
> It has the benefit that the change is recognized as a line replacement, so
> no extra {} are added when the call is in an if branch.
prev parent reply other threads:[~2024-01-22 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 6:20 Li Zhijian
2024-01-20 21:20 ` Julia Lawall
2024-01-21 10:40 ` [cocci] [v2] " Markus Elfring
2024-01-21 11:00 ` Julia Lawall
2024-01-21 11:04 ` Markus Elfring
2024-01-21 11:21 ` Julia Lawall
2024-01-21 12:03 ` Markus Elfring
2024-01-22 9:16 ` Markus Elfring
2024-01-22 3:29 ` Zhijian Li (Fujitsu) [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=d14443fd-96ee-4d94-a149-d81990f64de6@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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®