From: Kalle Valo <kvalo@codeaurora.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: Maya Erez <merez@codeaurora.org>,
YueHaibing <yuehaibing@huawei.com>,
<linux-wireless@vger.kernel.org>, <wil6210@qti.qualcomm.com>,
<kernel-janitors@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] wil6210: fix debugfs_simple_attr.cocci warnings
Date: Sat, 13 Oct 2018 17:29:12 +0000 (UTC) [thread overview]
Message-ID: <20181013172912.2923960116@smtp.codeaurora.org> (raw)
In-Reply-To: <1538737646-118337-1-git-send-email-yuehaibing@huawei.com>
YueHaibing <yuehaibing@huawei.com> wrote:
> Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
> for debugfs files.
>
> Semantic patch information:
> Rationale: DEFINE_SIMPLE_ATTRIBUTE + debugfs_create_file()
> imposes some significant overhead as compared to
> DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe().
>
> Generated by: scripts/coccinelle/api/debugfs/debugfs_simple_attr.cocci
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
f9dca154a4e4 wil6210: fix debugfs_simple_attr.cocci warnings
--
https://patchwork.kernel.org/patch/10627883/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-10-14 1:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 11:07 [PATCH] wil6210: fix debugfs_simple_attr.cocci warnings YueHaibing
[not found] ` <1538737646-118337-1-git-send-email-yuehaibing-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-10-05 11:04 ` Kalle Valo
2018-10-05 11:51 ` YueHaibing
[not found] ` <877eiw1wol.fsf-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-05 14:29 ` Julia Lawall
2018-10-06 12:11 ` Kalle Valo
2018-10-06 12:22 ` Julia Lawall
2018-10-06 12:54 ` Kalle Valo
2018-10-13 17:29 ` Kalle Valo [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=20181013172912.2923960116@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=merez@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=wil6210@qti.qualcomm.com \
--cc=yuehaibing@huawei.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 NNTP newsgroup(s).