mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] x86/its: Fix build errors when CONFIG_MODULES=n
Date: Tue, 13 May 2025 15:30:41 -0400	[thread overview]
Message-ID: <20250513153041.7bce37df@gandalf.local.home> (raw)
In-Reply-To: <2b706c51-5518-472b-b251-c7c8c39d3a1e@oracle.com>

On Wed, 14 May 2025 00:53:26 +0530
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com> wrote:

> Hi Steven,
> 
> 
> On 13/05/25 23:47, Steven Rostedt wrote:
> > On Mon, 12 May 2025 19:58:39 -0700
> > Eric Biggers <ebiggers@kernel.org> wrote:
> >   
> >> Fixes: 872df34d7c51 ("x86/its: Use dynamic thunks for indirect branches")
> >> Cc: stable@vger.kernel.org  
> > 
> > No need to Cc stable. This isn't even in Linus's tree.  
> 
> It is now(today) present I think: 
> https://github.com/torvalds/linux/commit/872df34d7c51a79523820ea6a14860398c639b87

Bah. My upstream repo gets updated every night via a cronjob, and that's
what I was looking at.

> 
> Greg queued this up for today's stable-rc which was released for Testing.

I didn't see any "stable" or "fixes" tag in the offending commit, so I
definitely didn't expect it to be in stable :-p


> 
> Informed him about this fix:
> 
> https://lore.kernel.org/all/88d537d6-57be-4fbc-9722-15997a022abb@oracle.com/

Thanks for letting me know.

-- Steve

  reply	other threads:[~2025-05-13 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  2:58 Eric Biggers
2025-05-13 18:06 ` Alexandre Chartre
2025-05-13 18:15 ` Steven Rostedt
2025-05-13 18:17 ` Steven Rostedt
2025-05-13 19:23   ` Harshit Mogalapalli
2025-05-13 19:30     ` Steven Rostedt [this message]
2025-05-13 18:54 ` Dave Hansen
2025-05-13 20:32   ` Dave Hansen
2025-05-13 21:36     ` Linus Torvalds

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=20250513153041.7bce37df@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=ebiggers@kernel.org \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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
all inboxes | Powered by JetHome®