mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Steve Wahl <steve.wahl@hpe.com>
Cc: Dimitri Sivanich <dimitri.sivanich@hpe.com>,
	Russ Anderson <russ.anderson@hpe.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/platform/uv: Use alternate source for socket to node data
Date: Thu, 7 Sep 2023 14:32:11 -0700	[thread overview]
Message-ID: <81ee91fa-5546-4ca8-e8bc-765174938fc5@intel.com> (raw)
In-Reply-To: <ZPo/z0TaWahjgglT@swahl-home.5wahls.com>

On 9/7/23 14:25, Steve Wahl wrote:
>> Does this need a stable@ tag when it gets applied?
> I hadn't thought about that.  I think it meets the requirements in
> stable-kernel-rules.rst.  And it looks like it should apply without
> conflicts or prerequisites.  So it probably should.  Is there a way to
> add a cc:stable tag at this point?

I can do it when I apply it.  I just wanted to make sure there wasn't a
good reason you left off the cc:stable.

  reply	other threads:[~2023-09-07 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 14:17 Steve Wahl
2023-08-28 21:22 ` Steve Wahl
2023-09-01 17:18 ` Dave Hansen
2023-09-01 19:01   ` Steve Wahl
2023-09-05 15:01     ` Steve Wahl
2023-09-07 20:57       ` Dave Hansen
2023-09-07 21:25         ` Steve Wahl
2023-09-07 21:32           ` Dave Hansen [this message]
2023-09-07 21:43             ` Steve Wahl

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=81ee91fa-5546-4ca8-e8bc-765174938fc5@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=russ.anderson@hpe.com \
    --cc=steve.wahl@hpe.com \
    --cc=tglx@linutronix.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®