From: Paolo Bonzini <pbonzini@redhat.com>
To: Nicolai Stange <nstange@suse.de>
Cc: Chen Wandun <chenwandun@huawei.com>,
rkrcmar@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] KVM: Fix debugfs_simple_attr.cocci warnings
Date: Thu, 9 Jan 2020 10:17:57 +0100 [thread overview]
Message-ID: <5d75e57a-4d04-e6b9-1bbd-a01072bfa6b1@redhat.com> (raw)
In-Reply-To: <87h816nsv9.fsf@suse.de>
On 08/01/20 11:29, Nicolai Stange wrote:
>
> How about introducing a
> #define debugfs_create_attr debugfs_create_file_unsafe
> instead to make those
> s/DEFINE_SIMPLE_ATTRIBUTE/DEFINE_DEBUGFS_ATTRIBUTE/
> patches look less scary?
I agree that could be worthwhile. My main complaint is the "scariness
factor" of the patches that convert DEFINE_SIMPLE_ATTRIBUTE to
DEFINE_DEBUGFS_ATTRIBUTE, and this change would alleviate that problem.
Thanks,
Paolo
prev parent reply other threads:[~2020-01-09 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 1:41 [PATCH next] KVM: Fix debugfs_simple_attr.cocci warnings Chen Wandun
2020-01-07 14:01 ` Paolo Bonzini
2020-01-08 10:29 ` Nicolai Stange
2020-01-09 9:17 ` Paolo Bonzini [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=5d75e57a-4d04-e6b9-1bbd-a01072bfa6b1@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=chenwandun@huawei.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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