mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: Borislav Petkov <bp@alien8.de>
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 7/7] x86: microcode: constify attribute_group structures.
Date: Thu, 20 Jul 2017 14:31:09 +0530	[thread overview]
Message-ID: <3e870042-56ec-8b12-98e7-2110c7b75ac5@gmail.com> (raw)
In-Reply-To: <20170720082850.GB18424@nazgul.tnic>

Hi,


On Thursday 20 July 2017 01:58 PM, Borislav Petkov wrote:
> On Thu, Jul 20, 2017 at 01:48:17PM +0530, Arvind Yadav wrote:
>> It's just show, how much bytes move from data segment to text segment.
>> ~arvind
>       3614	    545	   1560	   5719	   1657	x86/kernel/cpu/microcode/core.o
>
> 3614 + 545 = 4159
>
>       3742	    417	   1560	   5719	   1657	x86/kernel/cpu/microcode/core.o
>
> 3742 + 417 = 4159
>
> 3742 - 3614 = 128
>
> So 128 bytes moved to text.
Yes,
>
> I fail to see how this is relevant. Your commit message contains not
> really relevant info for such a simple change. Rather, it should just be
> a one-liner:
I have mentioned all this in commit message. I have added below
message in patch. Please check my patch.

"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."

> "Constify attribute_group structs because they don't change at runtime."
I can add this as subject. But we should avoid lengthy subject.
Even checkpatch.pl will through warning.
>
> That's it.
>
~arvind

  reply	other threads:[~2017-07-20  9:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  7:21 [PATCH 0/7] constify x86 " Arvind Yadav
2017-07-20  7:21 ` [PATCH 1/7] perf: x86: intel: uncore: constify " Arvind Yadav
2017-07-20  7:21 ` [PATCH 2/7] perf: x86: intel: uncore_nhmex: " Arvind Yadav
2017-07-20  7:21 ` [PATCH 3/7] perf: x86: intel: uncore_snb: " Arvind Yadav
2017-07-20  7:21 ` [PATCH 4/7] perf: x86: intel: uncore_snbep: " Arvind Yadav
2017-07-20  7:21 ` [PATCH 5/7] x86: ksysfs: " Arvind Yadav
2017-07-20  7:21 ` [PATCH 6/7] x86: therm_throt: " Arvind Yadav
2017-07-20  7:21 ` [PATCH 7/7] x86: microcode: " Arvind Yadav
2017-07-20  8:12   ` Borislav Petkov
2017-07-20  8:18     ` Arvind Yadav
2017-07-20  8:28       ` Borislav Petkov
2017-07-20  9:01         ` Arvind Yadav [this message]
2017-07-20 10:31           ` Borislav Petkov
2017-07-20 11:01             ` 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=3e870042-56ec-8b12-98e7-2110c7b75ac5@gmail.com \
    --to=arvind.yadav.cs@gmail.com \
    --cc=bp@alien8.de \
    --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

all inboxes | Powered by JetHome®