mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Jan H. Schönherr" <jan@schnhrr.de>,
	"Borislav Petkov" <bp@alien8.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	x86@kernel.org, "Thomas Lendacky" <Thomas.Lendacky@amd.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, it+linux-x86@molgen.mpg.de
Subject: Re: [PATCH 0/2] Fix TSC issues on (some) AMD Ryzen based systems
Date: Tue, 29 Jan 2019 23:31:26 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1901292329320.1950@nanos.tec.linutronix.de> (raw)
In-Reply-To: <986788f4-2a89-78a9-edee-3754dadba512@molgen.mpg.de>

Paul,

On Tue, 29 Jan 2019, Paul Menzel wrote:
> 
> Please do not forget to tag both patches for the stable releases
> by adding the tag.
> 
> > CC: stable@vger.kernel.org

That's not the way it works. The TSC one might go to stable eventually, but
the second one is a hack and surely goes nowhere in the current
form. Routing patches to stable is not a matter of works for me.

Thanks,

	tglx

      reply	other threads:[~2019-01-29 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 10:23 Jan H. Schönherr
2019-01-29 10:23 ` [PATCH 1/2] x86/tsc: Allow quick PIT calibration despite interruptions Jan H. Schönherr
     [not found]   ` <5C50558B.8060405@schnhrr.de>
2019-01-29 22:28     ` Thomas Gleixner
2019-02-12 11:57       ` Thomas Gleixner
2019-02-14 21:48         ` Jan H. Schönherr
2019-01-29 10:23 ` [PATCH 2/2] cpu/hotplug: Unfreeze sibling CPU first on resume from S3 Jan H. Schönherr
2019-01-29 23:02   ` Thomas Gleixner
2019-01-29 19:33 ` [PATCH 0/2] Fix TSC issues on (some) AMD Ryzen based systems Paul Menzel
2019-01-29 19:37   ` Paul Menzel
2019-01-29 22:31     ` Thomas Gleixner [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=alpine.DEB.2.21.1901292329320.1950@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=it+linux-x86@molgen.mpg.de \
    --cc=jan@schnhrr.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --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®