All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwan Velu <e.velu@criteo.com>
To: Greg KH <gregkh@linuxfoundation.org>, Borislav Petkov <bp@alien8.de>
Cc: stable <stable@vger.kernel.org>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>,
	"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
	"jiaxun.yang@flygoat.com" <jiaxun.yang@flygoat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sherry.hurwitz@amd.com" <sherry.hurwitz@amd.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
	"hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [tip:x86/cpu] x86/CPU/AMD: Set the CPB bit unconditionally on F17h
Date: Mon, 11 Mar 2019 16:32:50 +0000	[thread overview]
Message-ID: <3aa41b12-c796-fce4-41ee-cee0de7979cc@criteo.com> (raw)
In-Reply-To: <20190308102647.GA19469@kroah.com>


Le 08/03/2019 à 11:26, Greg KH a écrit :
> On Thu, Feb 21, 2019 at 01:25:23PM +0100, Borislav Petkov wrote:
>> On Thu, Feb 21, 2019 at 12:52:30PM +0100, Greg KH wrote:
>>> I would, but I do not see this patch in Linus's tree yet :)
>> You will soon :)
> I see it now, so it's now queued up, thanks.
>
> greg k-h
Thanks greg !

      reply	other threads:[~2019-03-11 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  3:00 [PATCH v2] x86/cpu/AMD: Fix CPB bit for more processors Jiaxun Yang
2019-01-18 15:48 ` [tip:x86/cpu] x86/CPU/AMD: Set the CPB bit unconditionally on F17h tip-bot for Jiaxun Yang
2019-02-20  8:53   ` Borislav Petkov
2019-02-21 11:52     ` Greg KH
2019-02-21 12:25       ` Borislav Petkov
2019-03-08 10:26         ` Greg KH
2019-03-11 16:32           ` Erwan Velu [this message]

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=3aa41b12-c796-fce4-41ee-cee0de7979cc@criteo.com \
    --to=e.velu@criteo.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=stable@vger.kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.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 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.