From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Salvatore Bonaccorso <carnil@debian.org>,
Pavel Machek <pavel@denx.de>,
Vignesh Raghavendra <vigneshr@ti.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
Daniel Wagner <daniel.wagner@suse.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
Mark Gross <markgross@kernel.org>,
Jeff Brady <jeffreyjbrady@gmail.com>
Subject: Re: [ANNOUNCE] 5.10.162-rt78
Date: Fri, 20 Jan 2023 14:04:15 +0100 [thread overview]
Message-ID: <Y8qRTwEnEJz0L4mm@linutronix.de> (raw)
In-Reply-To: <Y8qOOxON9Vfsek0l@uudg.org>
On 2023-01-20 09:51:07 [-0300], Luis Claudio R. Goncalves wrote:
> My question is: do you prefer renumbering the bits or the neat asm hack
> that Mike proposed?
That change, that was stable-backported, should have hit the devel tree
first. Why not sync with that?
> Luis
Sebastian
next prev parent reply other threads:[~2023-01-20 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 13:35 [ANNOUNCE] 5.10.162-rt78 Luis Claudio R. Goncalves
2023-01-19 8:32 ` Vignesh Raghavendra
2023-01-19 11:38 ` Pavel Machek
2023-01-19 12:37 ` Pavel Machek
2023-01-19 13:16 ` Luis Claudio R. Goncalves
2023-01-19 21:03 ` Salvatore Bonaccorso
2023-01-19 23:09 ` Jens Axboe
2023-01-20 3:44 ` Luis Claudio R. Goncalves
2023-01-20 3:49 ` Jens Axboe
2023-01-20 5:36 ` Salvatore Bonaccorso
2023-01-20 10:01 ` Daniel Wagner
2023-01-20 14:48 ` Jens Axboe
2023-01-20 12:51 ` Luis Claudio R. Goncalves
2023-01-20 13:04 ` Sebastian Andrzej Siewior [this message]
2023-01-20 15:37 ` Mark Rutland
2023-01-20 18:25 ` Luis Claudio R. Goncalves
2023-01-20 18:38 ` Salvatore Bonaccorso
2023-01-23 16:32 ` Mark Rutland
2023-01-28 8:24 ` Raghavendra, Vignesh
2023-01-20 6:01 ` Mike Galbraith
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=Y8qRTwEnEJz0L4mm@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=axboe@kernel.dk \
--cc=carnil@debian.org \
--cc=daniel.wagner@suse.com \
--cc=jeffreyjbrady@gmail.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=vigneshr@ti.com \
--cc=williams@redhat.com \
/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