From: Darren Hart <dvhart@infradead.org>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>,
joe@perches.com, kernel-janitors@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/26] intel_telemetry_debugfs: constify local structures
Date: Wed, 28 Sep 2016 16:52:35 -0700 [thread overview]
Message-ID: <20160928235235.GD7630@f23x64.localdomain> (raw)
In-Reply-To: <1473599168-30561-18-git-send-email-Julia.Lawall@lip6.fr>
On Sun, Sep 11, 2016 at 03:05:59PM +0200, Julia Lawall wrote:
Hi Julia,
> For structure types defined in the same file or local header files, find
> top-level static structure declarations that have the following
> properties:
> 1. Never reassigned.
> 2. Address never taken
Hrm. telem_apl_debugfs_conf is passed to the TELEM_DEBUGFS_CPU macro as the
second argument "data":
#define TELEM_DEBUGFS_CPU(model, data) \
{ X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, (unsigned long)&data}
And the address is taken, and later assigned to the debugfs_conf pointer.
The usage still seems OK, but did I misunderstand the conditions?
> 3. Not passed to a top-level macro call
> 4. No pointer or array-typed field passed to a function or stored in a
> variable.
> Declare structures having all of these properties as const.
>
> Done using Coccinelle.
> Based on a suggestion by Joe Perches <joe@perches.com>.
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
> The semantic patch seems too long for a commit log, but is in the cover
> letter.
>
> drivers/platform/x86/intel_telemetry_debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/intel_telemetry_debugfs.c b/drivers/platform/x86/intel_telemetry_debugfs.c
> index ef29f18..d0761f3 100644
> --- a/drivers/platform/x86/intel_telemetry_debugfs.c
> +++ b/drivers/platform/x86/intel_telemetry_debugfs.c
> @@ -297,7 +297,7 @@ struct telemetry_debugfs_conf {
>
> static struct telemetry_debugfs_conf *debugfs_conf;
>
> -static struct telemetry_debugfs_conf telem_apl_debugfs_conf = {
> +static const struct telemetry_debugfs_conf telem_apl_debugfs_conf = {
> .pss_idle_data = telem_apl_pss_idle_data,
> .pcs_idle_blkd_data = telem_apl_pcs_idle_blkd_data,
> .pcs_s0ix_blkd_data = telem_apl_pcs_s0ix_blkd_data,
>
>
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-09-28 23:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 13:05 [PATCH 00/26] constify local structures Julia Lawall
2016-09-11 13:05 ` [PATCH 17/26] intel_telemetry_debugfs: " Julia Lawall
2016-09-28 23:52 ` Darren Hart [this message]
2016-09-29 5:19 ` Julia Lawall
2016-09-30 0:07 ` Darren Hart
2016-09-11 13:06 ` [PATCH 18/26] intel_scu_ipc: " Julia Lawall
2016-09-12 12:37 ` Julia Lawall
[not found] ` <1473599168-30561-1-git-send-email-Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
2016-09-11 17:21 ` [PATCH 00/26] " Jarkko Sakkinen
2016-09-12 8:54 ` Julia Lawall
2016-09-12 13:16 ` Jarkko Sakkinen
2016-09-12 13:23 ` Julia Lawall
2016-09-12 13:43 ` Felipe Balbi
2016-09-12 13:52 ` Julia Lawall
2016-09-12 18:50 ` Jarkko Sakkinen
2016-09-12 13:57 ` Geert Uytterhoeven
2016-09-12 20:14 ` Jarkko Sakkinen
2016-09-12 21:11 ` Julia Lawall
2016-09-11 17:56 ` Joe Perches
2016-09-11 19:11 ` Julia Lawall
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=20160928235235.GD7630@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=Julia.Lawall@lip6.fr \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=souvik.k.chakravarty@intel.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