From: Borislav Petkov <bp@alien8.de>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, tony.luck@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/7] x86: therm_throt: constify attribute_group structures.
Date: Thu, 20 Jul 2017 17:58:53 +0200 [thread overview]
Message-ID: <20170720155853.GD20712@nazgul.tnic> (raw)
In-Reply-To: <1500550238-15655-7-git-send-email-arvind.yadav.cs@gmail.com>
On Thu, Jul 20, 2017 at 05:00:37PM +0530, Arvind Yadav wrote:
> 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>
> ---
> change in v2:
> Remove before/after size comparison from commit message.
>
> arch/x86/kernel/cpu/mcheck/therm_throt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This one and the next:
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2017-07-20 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 11:30 [PATCH v2 0/7] constify x86 attribute_group structures Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 1/7] perf: x86: intel: uncore: constify " Arvind Yadav
2017-08-18 9:33 ` [tip:x86/urgent] x86: Constify " tip-bot for Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 2/7] perf: x86: intel: uncore_nhmex: constify " Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 3/7] perf: x86: intel: uncore_snb: " Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 4/7] perf: x86: intel: uncore_snbep: " Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 5/7] x86: ksysfs: " Arvind Yadav
2017-07-20 11:30 ` [PATCH v2 6/7] x86: therm_throt: " Arvind Yadav
2017-07-20 15:58 ` Borislav Petkov [this message]
2017-07-20 11:30 ` [PATCH v2 7/7] x86: microcode: " Arvind Yadav
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=20170720155853.GD20712@nazgul.tnic \
--to=bp@alien8.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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