public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Len Brown <lenb@kernel.org>, Dave Hansen <dave.hansen@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	peterz@infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Len Brown <len.brown@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] x86/cpu: Add INTEL_LUNARLAKE_M to X86_BUG_MONITOR
Date: Sun, 01 Dec 2024 13:58:53 +0100	[thread overview]
Message-ID: <877c8jwodu.ffs@tglx> (raw)
In-Reply-To: <CAJvTdKmi6-nEwhq8edPw5g2b+ME2_HX+ctePpcPFoZPbNcXqhQ@mail.gmail.com>

On Thu, Nov 21 2024 at 05:22, Len Brown wrote:
> On Wed, Nov 20, 2024 at 3:21 PM Dave Hansen <dave.hansen@intel.com> wrote:
>> I'm not going to lose sleep over it, but as a policy, I think we should
>> backport CPU fixes to all the stable kernels. I don't feel like I have a
>> good enough handle on what kernels folks run on new systems to make a
>> prediction.
>
> FWIW, I sent a backport of a slightly earlier version of this patch,
> but all I got back was vitriol about violating the kernel Documentation on
> sending to stable.
>
> Maybe a native english speaker could re-write that Documentation,
> so that a native english speaker can understand it?

What's so hard to understand?

 There are three options to submit a change to -stable trees:

  1. Add a'stable tag' to the description of a patch you then submit for mainline
     inclusion.

  2. Ask the stable team to pick up a patch already mainlined.

  3. Submit a patch to the stable team that is equivalent to a change
     already mainlined.

Is very clear and understandable english, no?

#1    is the preferred one and only requires a "stable tag"

#2/#3 can only be done once the fix is upstream as they require the
      upstream commit id.

It's clearly spelled out in the detailed descriptions of the three
options.

Thanks,

        tglx

      reply	other threads:[~2024-12-01 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  2:07 [PATCH v3] x86/cpu: Add INTEL_LUNARLAKE_M to X86_BUG_MONITOR Len Brown
2024-11-13  9:05 ` Rafael J. Wysocki
2024-11-20 19:12 ` Dave Hansen
2024-11-20 20:08   ` Rafael J. Wysocki
2024-11-20 20:21     ` Dave Hansen
2024-11-21 10:22       ` Len Brown
2024-12-01 12:58         ` 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=877c8jwodu.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=dave.hansen@intel.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=stable@vger.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