From: Tom Rini <trini@konsulko.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org,
Joshua Thompson <funaho@jurai.org>,
Philip Blundell <philb@gnu.org>,
u-boot@lists.denx.de
Cc: Huan Wang <alison.wang@nxp.com>, Angelo Dureghello <angelo@sysam.it>
Subject: U-Boot support for M68K removal
Date: Fri, 27 Jan 2023 08:49:57 -0500 [thread overview]
Message-ID: <Y9PWhU7DVQCLP9EX@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Hey all (and especially the non-U-Boot folks / lists),
U-Boot has had support for the m68k architecture for practically forever
it seems like. Unfortunately, it's also been a few years now since I've
seen anyone active in reviewing general patches to the architecture and
doing the little things to keep it up to date and following best
practices. So I'm here asking, does anyone know someone interested in
maintaining U-Boot on m68k, for whatever platforms interest them?
Otherwise, sometime this year I'm likely to drop the architecture.
Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next reply other threads:[~2023-01-27 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:49 Tom Rini [this message]
2023-01-27 14:44 ` U-Boot support for M68K removal Geert Uytterhoeven
[not found] ` <CALJHbkBqdvJu8KGKbJ2eayhiP_t607AvuwgYidhLTPY7=Mt4Hg@mail.gmail.com>
2023-01-30 16:14 ` Tom Rini
2023-01-30 16:22 ` John Paul Adrian Glaubitz
2023-01-30 16:34 ` Tom Rini
2023-01-30 18:56 ` Eero Tamminen
2023-01-30 19:10 ` Geert Uytterhoeven
2023-01-30 19:31 ` Tom Rini
2023-01-30 21:50 ` Greg Ungerer
2023-01-30 22:04 ` Tom Rini
2023-01-31 7:25 ` Angelo Dureghello
2023-01-30 19:25 ` Angelo Dureghello
2023-02-04 15:55 ` John Paul Adrian Glaubitz
2023-02-06 8:14 ` Angelo Dureghello
2023-02-06 12:02 ` Greg Ungerer
2023-02-06 12:25 ` John Paul Adrian Glaubitz
2023-02-06 12:30 ` John Paul Adrian Glaubitz
2023-02-06 13:47 ` Greg Ungerer
2023-02-06 14:00 ` Greg Ungerer
2023-02-06 12:59 ` Angelo Dureghello
2023-02-06 13:49 ` Greg Ungerer
[not found] ` <CALJHbkCTbhBrn5_XLPBADswOdhwah7vz7eke_YOr-D1spVRmyQ@mail.gmail.com>
2023-01-30 19:32 ` Tom Rini
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=Y9PWhU7DVQCLP9EX@bill-the-cat \
--to=trini@konsulko.com \
--cc=alison.wang@nxp.com \
--cc=angelo@sysam.it \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=philb@gnu.org \
--cc=u-boot@lists.denx.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