From: "Arnd Bergmann" <arnd@arndb.de>
To: "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Andreas Larsson" <andreas@gaisler.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"David S . Miller" <davem@davemloft.net>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
sparclinux@vger.kernel.org,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] sparc: Use $(kecho) to announce kernel images being ready
Date: Tue, 19 Dec 2023 10:32:16 +0000 [thread overview]
Message-ID: <4e6d829f-e0d8-4e4b-839d-3ec1cfd8983b@app.fastmail.com> (raw)
In-Reply-To: <68e7ccc8e9e2e90765b94fcc3999d99a4e98fc8e.camel@physik.fu-berlin.de>
On Mon, Dec 18, 2023, at 21:02, John Paul Adrian Glaubitz wrote:
> On Mon, 2023-12-18 at 20:52 +0000, Arnd Bergmann wrote:
>
>> The most important bit here would be someone with the authority
>> or Ack or Nak a patch going into another git tree. Even if you
>> are sometimes wrong, that is still much better than no reply.
>
> Yep. And there are actually a number of very nice improvements from
> Oracle engineers for sparc64 that got never upstreamed. These include
> kexec support as well as support for hypervisor control from Linux.
>
> They can all be found in Oracle's Unbreakable Kernel Tree:
>
>> https://github.com/oracle/linux-uek/tree/uek4/qu7
>
> I have already reached out to one of the Oracle engineers and they would
> be happy to help us getting some of the patches merged upstream.
Ah, I didn't know there were so many patches that never made it in.
It does look like they were only in UEK4 (linux-4.1) but not ported
to the later kernels, so it's going to be more challenging to port
these to mainline than the set of leon3 patches that are already on
a recent baseline.
Arnd
prev parent reply other threads:[~2023-12-19 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:52 [PATCH] sparc: Use $(kecho) to announce kernel images being ready Uwe Kleine-König
2023-07-13 14:55 ` Sam Ravnborg
2023-12-04 11:05 ` Uwe Kleine-König
2023-12-04 11:14 ` John Paul Adrian Glaubitz
2023-12-04 13:06 ` Arnd Bergmann
2023-12-04 13:37 ` John Paul Adrian Glaubitz
2023-12-04 14:13 ` Arnd Bergmann
2023-12-05 18:05 ` Sam Ravnborg
2023-12-05 20:26 ` Sam Ravnborg
2023-12-06 9:31 ` John Paul Adrian Glaubitz
2023-12-07 16:49 ` Andreas Larsson
2023-12-18 20:52 ` Arnd Bergmann
2023-12-18 21:02 ` John Paul Adrian Glaubitz
2023-12-19 10:32 ` Arnd Bergmann [this message]
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=4e6d829f-e0d8-4e4b-839d-3ec1cfd8983b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).