From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Anders Roxell <anders.roxell@linaro.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
bigunclemax@gmail.com, cgel.zte@gmail.com,
chenjingwen6@huawei.com,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Corentin Labbe <clabbe@baylibre.com>,
danielhb413@gmail.com, Helge Deller <deller@gmx.de>,
farosas@linux.ibm.com, ganeshgr@linux.ibm.com,
Geoff Levand <geoff@infradead.org>,
guozhengkui@vivo.com, haren@linux.ibm.com,
hbathini@linux.ibm.com, hbh25y@gmail.com,
Jakob Koschel <jakobkoschel@gmail.com>,
jniethe5@gmail.com, Joe Lawrence <joe.lawrence@redhat.com>,
Kees Cook <keescook@chromium.org>,
kernel.noureddine@gmail.com, kjain@linux.ibm.com,
ldufour@linux.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
maddy@linux.ibm.com, mamatha4@linux.vnet.ibm.com,
Miroslav Benes <mbenes@suse.cz>,
mikey@neuling.org, Michal Suchanek <msuchanek@suse.de>,
nathanl@linux.ibm.com,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Nick Piggin <npiggin@gmail.com>,
oss@buserror.net, Paul Menzel <pmenzel@molgen.mpg.de>,
Petr Mladek <pmladek@suse.com>,
psampat@linux.ibm.com, Randy Dunlap <rdunlap@infradead.org>,
Ritesh Harjani <riteshh@linux.ibm.com>,
rmclure@linux.ibm.com, sachinp@linux.ibm.com,
sourabhjain@linux.ibm.com, tobias@waldekranz.com,
Thierry Reding <treding@nvidia.com>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
Vaibhav Jain <vaibhav@linux.ibm.com>,
wangborong@cdjrlc.com, Wedson Almeida Filho <wedsonaf@google.com>,
YueHaibing <yuehaibing@huawei.com>
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-5.18-1 tag
Date: Mon, 28 Mar 2022 20:07:13 +1100 [thread overview]
Message-ID: <87wngefnsu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CAHk-=whk4jihDM+zkhZPYRyNO0-YA1_-K9_NyC3EDsX+gkxC-w@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, Mar 25, 2022 at 3:25 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Livepatch support for 32-bit is probably the standout new feature, otherwise mostly just
>> lots of bits and pieces all over the board.
>
> Heh. I would have expected 32-bit ppc to be entirely legacy by now, so
> it's a bit surprising to see that being a standout feature.
We still get the odd bug report from people running mainline, or recent
stable kernels, on 32-bit.
And obviously Christophe has been doing lots of work on the Linux side,
so in that sense 32-bit is alive and well.
Having said that I don't think we'll see any new 32-bit CPU designs, so
the clock is slowly ticking.
> That said:
>
>> There's a series of commits cleaning up function descriptor handling,
>
> For some reason I also thought that powerpc had actually moved away
> from function descriptors, so I'm clearly not keeping up with the
> times.
No you're right, we have moved away from them, but not entirely.
Functions descriptors are still used for 64-bit big endian, but they're
not used for 64-bit little endian, or 32-bit.
cheers
next prev parent reply other threads:[~2022-03-28 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 10:25 [GIT PULL] Please pull powerpc/linux.git powerpc-5.18-1 tag Michael Ellerman
2022-03-25 16:49 ` Linus Torvalds
2022-03-28 9:07 ` Michael Ellerman [this message]
2022-03-30 11:27 ` Michal Suchánek
2022-03-30 13:21 ` Michael Ellerman
2022-03-30 13:44 ` Arnd Bergmann
2022-03-30 17:07 ` Segher Boessenkool
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=87wngefnsu.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Julia.Lawall@inria.fr \
--cc=aik@ozlabs.ru \
--cc=anders.roxell@linaro.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bigunclemax@gmail.com \
--cc=cgel.zte@gmail.com \
--cc=chenjingwen6@huawei.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=christophe.leroy@csgroup.eu \
--cc=clabbe@baylibre.com \
--cc=danielhb413@gmail.com \
--cc=deller@gmx.de \
--cc=farosas@linux.ibm.com \
--cc=ganeshgr@linux.ibm.com \
--cc=geoff@infradead.org \
--cc=guozhengkui@vivo.com \
--cc=haren@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=hbh25y@gmail.com \
--cc=jakobkoschel@gmail.com \
--cc=jniethe5@gmail.com \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel.noureddine@gmail.com \
--cc=kjain@linux.ibm.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mamatha4@linux.vnet.ibm.com \
--cc=mbenes@suse.cz \
--cc=mikey@neuling.org \
--cc=msuchanek@suse.de \
--cc=nathanl@linux.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=oss@buserror.net \
--cc=pmenzel@molgen.mpg.de \
--cc=pmladek@suse.com \
--cc=psampat@linux.ibm.com \
--cc=rdunlap@infradead.org \
--cc=riteshh@linux.ibm.com \
--cc=rmclure@linux.ibm.com \
--cc=sachinp@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=tobias@waldekranz.com \
--cc=torvalds@linux-foundation.org \
--cc=treding@nvidia.com \
--cc=unixbhaskar@gmail.com \
--cc=vaibhav@linux.ibm.com \
--cc=wangborong@cdjrlc.com \
--cc=wedsonaf@google.com \
--cc=yuehaibing@huawei.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