From: Markus Elfring <Markus.Elfring@web.de>
To: Sean Christopherson <seanjc@google.com>,
cocci@inria.fr, kernel-janitors@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolai Stange <nicstange@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [cocci] [PATCH] Revert "debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage"
Date: Wed, 12 Jul 2023 09:12:19 +0200 [thread overview]
Message-ID: <fd1959e5-b0c7-0d0a-d037-d5e05b550765@web.de> (raw)
In-Reply-To: <ZK1jYI/wyaxWnXrz@google.com>
>>> Regardless of whether or not the
>>> "significant overhead" incurred by debugfs_create_file() is actually
>>> meaningful, warnings from the script have led to a rash of low-quality
>>> patches that have sowed confusion and consumed maintainer time for little
>>> to no benefit. There have been no less than four attempts to "fix" KVM,
>>> and a quick search on lore shows that KVM is not alone.
>>
>> Will such information trigger any further clarification?
>
> I don't quite follow the question. What information, and what clarification?
I imagine that additional experiences can be shared and discussed for
a contribution by Nicolai Stange from 2016-03-22.
debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci?id=5103068eaca290f890a30aae70085fac44cecaf6
https://lore.kernel.org/cocci/1458652280-19785-5-git-send-email-nicstange@gmail.com/
https://lkml.org/lkml/2016/3/22/412
Regards,
Markus
prev parent reply other threads:[~2023-07-12 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 17:06 [cocci] [PATCH] Revert "debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage" Sean Christopherson
2023-07-10 17:12 ` Greg Kroah-Hartman
2023-07-11 5:50 ` Markus Elfring
[not found] ` <ZK1jYI/wyaxWnXrz@google.com>
2023-07-12 7:12 ` Markus Elfring [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=fd1959e5-b0c7-0d0a-d037-d5e05b550765@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=nicstange@gmail.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).