From: Markus Elfring <Markus.Elfring@web.de>
To: "Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org, kernel-janitors@vger.kernel.org,
cocci@inria.fr
Cc: Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] cgroup: Use seq_putc() in three functions
Date: Tue, 23 Jul 2024 12:50:22 +0200 [thread overview]
Message-ID: <57cc9da4-93ad-4279-a175-2e291ccc8a47@web.de> (raw)
In-Reply-To: <mbv6jl67qw43ruzf55yzgdo7zrusvuod2c3b7cfgliypyh7pgf@mqneyza5cffr>
>> This issue was transformed by using the Coccinelle software.
>
> Maybe that would better fit under scripts/coccinelle/misc for optional checking.
Would you like to support any corresponding developments also according to
the coccicheck tool?
Regards,
Markus
parent reply other threads:[~2024-07-23 10:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mbv6jl67qw43ruzf55yzgdo7zrusvuod2c3b7cfgliypyh7pgf@mqneyza5cffr>]
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=57cc9da4-93ad-4279-a175-2e291ccc8a47@web.de \
--to=markus.elfring@web.de \
--cc=cgroups@vger.kernel.org \
--cc=cocci@inria.fr \
--cc=hannes@cmpxchg.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.com \
--cc=tj@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).