From: Tom Rini <trini@konsulko.com>
To: Angelo Dureghello <angelo.dureghello@timesys.com>
Cc: 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, Huan Wang <alison.wang@nxp.com>
Subject: Re: U-Boot support for M68K removal
Date: Mon, 30 Jan 2023 11:14:19 -0500 [thread overview]
Message-ID: <Y9fs2wH4WHIzae5r@bill-the-cat> (raw)
In-Reply-To: <CALJHbkBqdvJu8KGKbJ2eayhiP_t607AvuwgYidhLTPY7=Mt4Hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Mon, Jan 30, 2023 at 01:49:11PM +0100, Angelo Dureghello wrote:
> Hi Tom and all,
>
> really have to apologize, had hard times these last 2 years
> and couldn't follow at all the activity, i am totally culprit
> and responsible.
>
> Now i can jump back on following, if there is any sense
> in keeping m68k/coldfire.
> Let me know, if ok i start back checking all old patches
> from tonight. Also, will have to update my email and rebase
> to master.
I'm glad you're back. I think the first thing to do would be to confirm
that U-Boot still works on at least some supported board, then
confirming you can still access
https://source.denx.de/u-boot/custodians/u-boot-coldfire
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-30 16:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:49 U-Boot support for M68K removal Tom Rini
2023-01-27 14:44 ` Geert Uytterhoeven
2023-01-30 12:49 ` Angelo Dureghello
2023-01-30 16:14 ` Tom Rini [this message]
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-07 21:48 ` Angelo Dureghello
2023-02-06 12:59 ` Angelo Dureghello
2023-02-06 13:49 ` Greg Ungerer
2023-01-30 19:22 ` Angelo Dureghello
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=Y9fs2wH4WHIzae5r@bill-the-cat \
--to=trini@konsulko.com \
--cc=alison.wang@nxp.com \
--cc=angelo.dureghello@timesys.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.