All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gross, Mark" <mark.gross@intel.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/3] char: tlclk: constify attribute_group structures.
Date: Wed, 2 Aug 2017 18:15:54 +0000	[thread overview]
Message-ID: <BD75D217E5BAC84080F8EFB2582976379E82B7B6@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <1501672745-2951-2-git-send-email-arvind.yadav.cs@gmail.com>

The driver doesn't seem to touch the name field after its defined it looks ok functionally.  

Note: I am not a fan of const declarations in the C language.  It's too complicated when we get into casting and pointers to structures.

I'm not sure there is a lot of value in being pedantic on a few users of attribute_group structures.  I'm thinking this change should be all or nothing and change core function prototypes to create warnings if they are not used with properly defined const 's.  Otherwise this is just a cosmetic change of minimal value to a subset of drivers.   

FWIW there does seem to be a good number (cscope finds 1700+) of attribute_group users across the kernel and a good number of them are not using const.  If you go down this pedantic path I don't think you should at just 3 drivers.

Reviewed-by: mark gross <mark.gross@intel.com>

--mark

> -----Original Message-----
> From: Arvind Yadav [mailto:arvind.yadav.cs@gmail.com]
> Sent: Wednesday, August 2, 2017 4:19 AM
> To: arnd@arndb.de; gregkh@linuxfoundation.org; Gross, Mark
> <mark.gross@intel.com>
> Cc: linux-kernel@vger.kernel.org
> Subject: [PATCH 1/3] char: tlclk: constify attribute_group structures.
> 
> attribute_group are not supposed to change at runtime. All functions working
> with attribute_group provided by <linux/sysfs.h> work with const
> attribute_group. So mark the non-const structs as const.
> 
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
> ---
>  drivers/char/tlclk.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/char/tlclk.c b/drivers/char/tlclk.c index 572a517..6210bff
> 100644
> --- a/drivers/char/tlclk.c
> +++ b/drivers/char/tlclk.c
> @@ -766,7 +766,7 @@ static ssize_t store_reset (struct device *d,
>  	NULL
>  };
> 
> -static struct attribute_group tlclk_attribute_group = {
> +static const struct attribute_group tlclk_attribute_group = {
>  	.name = NULL,		/* put in device directory */
>  	.attrs = tlclk_sysfs_entries,
>  };
> --
> 1.9.1

  reply	other threads:[~2017-08-02 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 11:19 [PATCH 0/3] constify char attribute_group structures Arvind Yadav
2017-08-02 11:19 ` [PATCH 1/3] char: tlclk: constify " Arvind Yadav
2017-08-02 18:15   ` Gross, Mark [this message]
2017-08-02 17:56 ` [PATCH 0/3] constify char " Gross, Mark
2017-08-03  5:34   ` Arvind Yadav
2017-08-03 12:37     ` Gross, Mark

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=BD75D217E5BAC84080F8EFB2582976379E82B7B6@ORSMSX112.amr.corp.intel.com \
    --to=mark.gross@intel.com \
    --cc=arnd@arndb.de \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.