All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	James Morse <james.morse@arm.com>
Subject: Re: [GIT PULL] x86/cache updates for 4.21
Date: Fri, 28 Dec 2018 13:49:04 +0100	[thread overview]
Message-ID: <20181228124904.GC20003@gmail.com> (raw)
In-Reply-To: <20181226205616.GA4557@zn.tnic>


* Borislav Petkov <bp@suse.de> wrote:

> On Wed, Dec 26, 2018 at 12:26:12PM -0800, Linus Torvalds wrote:
> > I've pulled this, but I think the new config option name is bad.
> > 
> > I think it should probably have been called "X86_RESCTRL" instead of
> > just "RESCTRL". That's way too generic a name for something that is
> > (at least currently) very much an x86 feature.
> 
> Right you are...

... and it's almost as if someone complained about this already:

   https://lkml.org/lkml/2018/11/23/389

   "Also, the Kconfig space, when it gets extended with the AMD bits, should
    probably follow the same nomenclature: CONFIG_X86_CPU_RESOURCE_CONTROL=yor such."

;-)

Anyway, I kind of dropped the ball after that first round of complaints, 
should have looked again.

Thanks,

	Ingo

  parent reply	other threads:[~2018-12-28 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23 12:48 [GIT PULL] x86/cache updates for 4.21 Borislav Petkov
2018-12-26 20:26 ` Linus Torvalds
2018-12-26 20:56   ` Borislav Petkov
2018-12-26 21:01     ` Linus Torvalds
2018-12-28 12:49     ` Ingo Molnar [this message]
2019-01-08 17:14       ` [PATCH] x86/cache: Rename config option to CONFIG_X86_RESCTRL Borislav Petkov
2019-01-08 17:34         ` Linus Torvalds
2019-01-09 10:03         ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2019-01-09 17:03         ` [PATCH] " Moger, Babu
2018-12-26 21:10 ` [GIT PULL] x86/cache updates for 4.21 pr-tracker-bot

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=20181228124904.GC20003@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.