public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Oleksandr G Zhadan <oleks@arcturusnetworks.com>
Cc: sjg@chromium.org, u-boot-request@lists.denx.de,
	u-boot@lists.denx.de,
	"arcsupport@ArcturusNetworks.com"
	<arcsupport@ArcturusNetworks.com>
Subject: Re: U-Boot Digest, Vol 158, Issue 63
Date: Wed, 8 Sep 2021 10:25:21 -0400	[thread overview]
Message-ID: <20210908142521.GE12964@bill-the-cat> (raw)
In-Reply-To: <20210805203119.GQ858@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Thu, Aug 05, 2021 at 04:31:19PM -0400, Tom Rini wrote:
> On Tue, Aug 03, 2021 at 09:21:57AM -0400, Oleksandr G Zhadan wrote:
> 
> > Hi Tom,
> > 
> > Thanks for the quick notes.
> > 
> > As I already mentioned, unfortunately, I did not notice any "warnings" in
> > time - we haven’t been building the bootloader recently, but our customer is
> > using it.
> > 
> > My only concern is the removal of support for the uCP1020 board. This
> > product is not dead and we would like to leave it on the u-boot host.
> > 
> > Please give us a couple of weeks to fix this (after I get back from
> > vacation).
> 
> I think this, along with taking most of Simon's series (such tat uCP1020
> still builds) is the best path forward right now.  I would rather see a
> series you've tested to update the platform soon than to attempt it
> myself now.

So it's been a little over a month.  Where do things stand on this?
Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2021-09-08 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1076.1627306815.660.u-boot@lists.denx.de>
2021-07-28 16:22 ` U-Boot Digest, Vol 158, Issue 63 Oleksandr G Zhadan
2021-07-28 16:43   ` Tom Rini
2021-08-03 13:21     ` Oleksandr G Zhadan
2021-08-05 20:31       ` Tom Rini
2021-09-08 14:25         ` Tom Rini [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=20210908142521.GE12964@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=arcsupport@ArcturusNetworks.com \
    --cc=oleks@arcturusnetworks.com \
    --cc=sjg@chromium.org \
    --cc=u-boot-request@lists.denx.de \
    --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