From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: "Gross, Mark" <mark.gross@intel.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 0/3] constify char attribute_group structures
Date: Thu, 3 Aug 2017 11:04:33 +0530 [thread overview]
Message-ID: <24f4fc72-47d9-ce26-18cf-abd8f5af4bcf@gmail.com> (raw)
In-Reply-To: <BD75D217E5BAC84080F8EFB2582976379E82B62C@ORSMSX112.amr.corp.intel.com>
Hi Mark,
On Wednesday 02 August 2017 11:26 PM, Gross, Mark wrote:
> Why stop at these 3 users of attribute_group?
I am doing for all. This changes is only for char user. Few patch are
under review and few are merged. Rest all I will send.
~arvind
> --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 0/3] constify char 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.
>
> Arvind Yadav (3):
> [PATCH 1/3] char: tlclk: constify attribute_group structures.
> [PATCH 2/3] char: tpm: constify attribute_group structures.
> [PATCH 3/3] char: virtio: constify attribute_group structures.
>
> drivers/char/tlclk.c | 2 +-
> drivers/char/tpm/tpm_ppi.c | 2 +-
> drivers/char/virtio_console.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-08-03 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 11:19 Arvind Yadav
2017-08-02 11:19 ` [PATCH 1/3] char: tlclk: constify " Arvind Yadav
2017-08-02 18:15 ` Gross, Mark
2017-08-02 17:56 ` [PATCH 0/3] constify char " Gross, Mark
2017-08-03 5:34 ` Arvind Yadav [this message]
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=24f4fc72-47d9-ce26-18cf-abd8f5af4bcf@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@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
all inboxes | Powered by JetHome®