From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: mm-commits@vger.kernel.org, will@kernel.org, vgupta@kernel.org,
urezki@gmail.com, tsbogend@alpha.franken.de, tglx@linutronix.de,
surenb@google.com, song@kernel.org, shorne@gmail.com,
rostedt@goodmis.org, richard@nod.at, peterz@infradead.org,
palmer@dabbelt.com, oleg@redhat.com, mpe@ellerman.id.au,
monstr@monstr.eu, mingo@redhat.com, mhiramat@kernel.org,
mcgrof@kernel.org, mattst88@gmail.com, mark.rutland@arm.com,
luto@kernel.org, linux@armlinux.org.uk, Liam.Howlett@oracle.com,
kent.overstreet@linux.dev, kdevops@lists.linux.dev,
johannes@sipsolutions.net, jcmvbkbc@gmail.com, hch@lst.de,
guoren@kernel.org, glaubitz@physik.fu-berlin.de,
geert@linux-m68k.org, dinguyen@kernel.org, deller@gmx.de,
dave.hansen@linux.intel.com, christophe.leroy@csgroup.eu,
chenhuacai@kernel.org, catalin.marinas@arm.com, bp@alien8.de,
bcain@quicinc.com, arnd@arndb.de, ardb@kernel.org,
andreas@gaisler.com
Subject: Re: [merged mm-stable] x86-module-prepare-module-loading-for-rox-allocations-of-text.patch removed from -mm tree
Date: Wed, 6 Nov 2024 13:30:09 -0800 [thread overview]
Message-ID: <20241106133009.ea62f45c0b7e6b0d400e4a22@linux-foundation.org> (raw)
In-Reply-To: <ZysRwR29Ji8CcbXc@kernel.org>
On Wed, 6 Nov 2024 08:50:41 +0200 Mike Rapoport <rppt@kernel.org> wrote:
> Hi Andrew,
>
> Yesterday Nathan discovered and I fixed another small issue with fineibt.
> I suspect it's too late to add this as a fixup, so here's a formal patch
> with the fix.
Thanks. I only moved this series into mm-stable yesterday so I'll do
the rebase and get this fixup integrated in the cleaner way.
next prev parent reply other threads:[~2024-11-06 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:00 [merged mm-stable] x86-module-prepare-module-loading-for-rox-allocations-of-text.patch removed from -mm tree Andrew Morton
2024-11-06 6:50 ` Mike Rapoport
2024-11-06 21:30 ` Andrew Morton [this message]
2024-12-05 8:41 ` Peter Zijlstra
2024-12-06 10:39 ` Mike Rapoport
2024-12-09 8:38 ` Peter Zijlstra
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=20241106133009.ea62f45c0b7e6b0d400e4a22@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=andreas@gaisler.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bcain@quicinc.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=deller@gmx.de \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guoren@kernel.org \
--cc=hch@lst.de \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kdevops@lists.linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux@armlinux.org.uk \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mattst88@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shorne@gmail.com \
--cc=song@kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=urezki@gmail.com \
--cc=vgupta@kernel.org \
--cc=will@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