From: Hans de Goede <hdegoede@redhat.com>
To: "Markus Elfring" <Markus.Elfring@web.de>,
"Cong Liu" <liucong2@kylinos.cn>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v2] platform/x86/amd/pmf: Fix memory leak in amd_pmf_get_pb_data()
Date: Mon, 29 Jan 2024 09:59:11 +0100 [thread overview]
Message-ID: <bbcf1b06-2a65-4f87-b15a-583a668dfc1e@redhat.com> (raw)
In-Reply-To: <2b3b4754-4c20-48ef-9844-f5db6a7f527e@web.de>
Hi,
On 1/28/24 11:45, Markus Elfring wrote:
>> Thank you for your patch/series, I've applied this patch
>> (series) to my review-hans branch:
>> https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
>>
>> Note it will show up in the pdx86 review-hans branch once I've
>> pushed my local branch there, which might take a while.
>
> Will development interests grow for the application of known scripts
> also according to the semantic patch language?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?h=v6.8-rc1#n71
Markus,
I'm not sure what your question here is?
Is it: "Will coccinelle scripts be run as part of the regular patch
test/merge workflow?" then the answer is that there are no plans
that I'm aware of to do that at this moment.
If such a thing were to be done, IMHO it would be best to have one
of the existing CI systems like e.h. Intel's LKP test bot run this
on linux-next, or on all the trees LKP already monitors.
And it does sound like something interesting to do, but someone
would need to actually setup and maintain such a CI system.
If the question is: "Are patches generated by coccinelle welcome?"
then the answer is "Yes patches generated by coccinelle are very
much welcome".
Regards,
Hans
next prev parent reply other threads:[~2024-01-29 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 1:11 [PATCH] platform/x86/amd/pmf: Fix memory leak in amd_pmf_get_pb_data() Cong Liu
2024-01-23 14:37 ` Shyam Sundar S K
2024-01-24 1:29 ` [PATCH v2] " Cong Liu
2024-01-26 19:16 ` Hans de Goede
2024-01-28 10:45 ` [v2] " Markus Elfring
2024-01-29 8:59 ` Hans de Goede [this message]
2024-01-29 9:52 ` Markus Elfring
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=bbcf1b06-2a65-4f87-b15a-583a668dfc1e@redhat.com \
--to=hdegoede@redhat.com \
--cc=Markus.Elfring@web.de \
--cc=Shyam-sundar.S-k@amd.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liucong2@kylinos.cn \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.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