From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"David S . Miller" <davem@davemloft.net>,
"Andreas Larsson" <andreas@gaisler.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, 5 Dec 2023 19:05:06 +0100 [thread overview]
Message-ID: <20231205180506.GA242352@ravnborg.org> (raw)
In-Reply-To: <add3c37a-08ef-41e1-b717-091d9bffd66a@app.fastmail.com>
Hi Arnd.
On Mon, Dec 04, 2023 at 02:06:02PM +0100, Arnd Bergmann wrote:
> I would also
> suggest raising the minimum SPARC32 level to that of
> leon3 (SPARCv8e with CAS), which is what glibc requires
> anyway for futex().
Agreed, it is long time since I got any indications that people
actually use these old machines.
The sparc32 machines I have, have not been powered up for several years
now, and they were only used to test new kernels on anyway.
I sent out a small patch series to do more or less what you suggested
maybe one year ago. Back then the resistance was only from nostalgic
people (like myself) and no real users.
If you or anyone moves forward removing the non-leon sparc32 support
then starting new would be the best approach, I do not think it makes
sense to dig up my old patch set.
Sam
next prev parent reply other threads:[~2023-12-05 18:06 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 [this message]
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
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=20231205180506.GA242352@ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--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