mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-rt-devel@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Maarten Lankhorst <dev@lankhorst.se>
Subject: Re: [ANNOUNCE] v7.3-rc4-rt1
Date: Fri, 2 Oct 2026 10:14:51 +0530	[thread overview]
Message-ID: <37b02446-1e54-4ea1-9532-11056053de6c@linux.ibm.com> (raw)
In-Reply-To: <20260922144152.x2J3_tNz@linutronix.de>



On 9/22/26 8:11 PM, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
> 
> I'm pleased to announce the v7.3-rc4-rt1 patch set.
> 
> Changes since v7.2-rt5:
> 
>    - Rebase to v7.3-rc4
> 
> The printk related changes are all gone. What is left in the queue is
> PowerPC, i915 and a sysfs file:
> - PowerPC
>    Some progress has been made. What is left is a pseries related MMU
>    change, a patch dropping KVM_MPIC (which is e500 only) and a stack
>    protector related workaround.
>    The stack protector workaround might work with a different fix since
>    only arch/powerpc is using boot_init_stack_canary().
> 

Thanks Sebastian.

It is nice to see a little progress has been made atleast.
But it was mostly my mistake that I couldn't get time to work on it.

Let me see if we can atleast get these ppc patches upstream.
Most seems sensible to me.

But then would come heavy lifting on function and performance verification.
That's a different beast altogether.

  reply	other threads:[~2026-10-02  4:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 14:41 Sebastian Andrzej Siewior
2026-10-02  4:44 ` Shrikanth Hegde [this message]
2026-10-02  6:34   ` Sebastian Andrzej Siewior

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=37b02446-1e54-4ea1-9532-11056053de6c@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=bigeasy@linutronix.de \
    --cc=dev@lankhorst.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®