From: Markus Elfring <Markus.Elfring@web.de>
To: Joel Granados <joel.granados@kernel.org>, linux-fsdevel@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>, Kees Cook <kees@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Joel Granados <j.granados@samsung.com>
Subject: Re: [v2] sysctl: Reduce dput(child) calls in proc_sys_fill_cache()
Date: Mon, 28 Oct 2024 13:56:08 +0100 [thread overview]
Message-ID: <4e6a5dcd-7870-4d1d-a29a-a3749af588fa@web.de> (raw)
In-Reply-To: <fpyvxkkhyv7gqbwayxmcglf2jh6gs65brbtojxxtpief4nm35g@l2jq7oab7p3p>
…
>> This issue was transformed by using a script for the
>> semantic patch language like the following.
>> <SmPL>
> Aren't you missing a "virtual patch" here?
Yes.
I presented an SmPL script example which would not be directly used
for the tool “coccicheck”.
> Is there another way to run it besides this command:
Another command example:
time spatch -timeout 23 -j4 --chunksize 1 --no-loops -dir . …/Projekte/Coccinelle/janitor/avoid_duplicate_function_call2.cocci > …/Projekte/Bau/Linux/scripts/Coccinelle/tuning1/next/20240913/avoid_duplicate_function_call2-no_loops.diff 2> …/Projekte/Bau/Linux/scripts/Coccinelle/tuning1/next/20240913/avoid_duplicate_function_call2-no_loops-errors.txt
Regards,
Markus
next prev parent reply other threads:[~2024-10-28 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 8:20 [PATCH] sysctl: Reduce dput(child) calls in proc_sys_fill_cache() Markus Elfring
2024-10-23 11:11 ` Joel Granados
2024-10-23 12:10 ` Markus Elfring
2024-10-23 13:20 ` Joel Granados
2024-10-23 15:27 ` [PATCH v2] " Markus Elfring
2024-10-28 9:23 ` Joel Granados
2024-10-28 12:56 ` Markus Elfring [this message]
2024-10-31 10:19 ` Joel Granados
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=4e6a5dcd-7870-4d1d-a29a-a3749af588fa@web.de \
--to=markus.elfring@web.de \
--cc=j.granados@samsung.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.