From: Sudeep Holla <sudeep.holla@arm.com>
To: Borislav Petkov <bp@suse.de>
Cc: Sudeep Holla <sudeep.holla@arm.com>, Tejun Heo <tj@kernel.org>,
Andre Przywara <Andre.Przywara@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH RFT v2] x86: move cacheinfo sysfs to generic cacheinfo infrastructure
Date: Wed, 04 Mar 2015 11:35:26 +0000 [thread overview]
Message-ID: <54F6EDFE.2040305@arm.com> (raw)
In-Reply-To: <20150304112740.GB3663@pd.tnic>
On 04/03/15 11:27, Borislav Petkov wrote:
> On Wed, Mar 04, 2015 at 11:15:49AM +0000, Sudeep Holla wrote:
>> I can do that, but wouldn't that add confusion as this commit is not
>> changing that behaviour. It's already changed in v4.0-rc1
>
> Nah, this would add a reference to the fact that the cpumask format is
> not really a stable thing and thus cannot be considered a userpsace
> regression. And having this info is important IMO in case someone is
> wondering in the future.
>
Thanks for clarifying, will add that info. Now I think it completely
makes sense especially since this commit will be the first target when
user-space first notice this cpumask format change.
> In general, having more and even redundant info in the commit messages
> is much better than having less info. I can't count the times I've been
> staring at a one-liner commit message and trying to rhyme up what was
> the purpose of doing it this way.
>
> So more is more, in this case. :-)
>
Agreed :)
--
Regards,
Sudeep
next prev parent reply other threads:[~2015-03-04 11:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 7:50 [PATCH RFT] " Sudeep Holla
2015-01-23 13:55 ` Thomas Gleixner
2015-01-23 18:15 ` Borislav Petkov
2015-02-23 16:36 ` Sudeep Holla
2015-02-23 18:14 ` [PATCH RFT v2] " Sudeep Holla
2015-02-24 7:58 ` Ingo Molnar
2015-02-24 9:30 ` Sudeep Holla
2015-02-24 17:57 ` Borislav Petkov
2015-02-24 18:09 ` Sudeep Holla
2015-02-24 18:58 ` Borislav Petkov
2015-03-01 22:39 ` Andre Przywara
2015-03-02 10:17 ` Sudeep Holla
2015-03-03 18:45 ` Borislav Petkov
2015-03-03 18:53 ` Tejun Heo
2015-03-03 18:57 ` Borislav Petkov
2015-03-04 11:15 ` Sudeep Holla
2015-03-04 11:27 ` Borislav Petkov
2015-03-04 11:35 ` Sudeep Holla [this message]
2015-03-04 9:52 ` Sudeep Holla
2015-03-04 12:00 ` [PATCH v3] " Sudeep Holla
2015-03-04 12:27 ` Borislav Petkov
2015-03-05 8:16 ` Borislav Petkov
2015-03-05 9:28 ` Sudeep Holla
2015-03-10 11:37 ` Borislav Petkov
2015-03-10 11:53 ` Sudeep Holla
2015-03-10 14:22 ` Sudeep Holla
2015-03-10 14:26 ` Borislav Petkov
2015-03-10 14:35 ` Sudeep Holla
2015-03-11 13:36 ` Borislav Petkov
2015-03-11 15:44 ` Sudeep Holla
2015-03-11 20:23 ` Borislav Petkov
2015-03-09 14:46 ` [tip:x86/cpu] x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure tip-bot for Sudeep Holla
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=54F6EDFE.2040305@arm.com \
--to=sudeep.holla@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--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
Powered by JetHome