All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Rick Chen <rickchen36@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>, rick <rick@andestech.com>
Subject: Re: [PATCH] nds32: Remove the architecture
Date: Fri, 22 Apr 2022 08:14:08 -0400	[thread overview]
Message-ID: <20220422121408.GY3045430@bill-the-cat> (raw)
In-Reply-To: <CAN5B=eJko7J9q0Yd=doa8TtAoGc-xaDeVTRokx75y2j1myXDpQ@mail.gmail.com>

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

On Fri, Apr 22, 2022 at 04:45:28PM +0800, Rick Chen wrote:
> Hi, Tom,
> 
> > From: Tom Rini <trini@konsulko.com>
> > Sent: Wednesday, April 20, 2022 2:43 AM
> > To: u-boot@lists.denx.de; Rick Jian-Zhi Chen(陳建志) <rick@andestech.com>
> > Subject: Re: [PATCH] nds32: Remove the architecture
> >
> > On Wed, Apr 06, 2022 at 09:21:25AM -0400, Tom Rini wrote:
> >
> > > As removal of nds32 has been ack'd for the Linux kernel, remove
> > > support here as well.
> > >
> > > Cc: Rick Chen <rick@andestech.com>
> > > Signed-off-by: Tom Rini <trini@konsulko.com>
> >
> > Ping?
> 
> Sorry for the late responses.
> 
> Thanks for the information.

Sorry, is that an ack?

-- 
Tom

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

  reply	other threads:[~2022-04-22 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 13:21 [PATCH] nds32: Remove the architecture Tom Rini
2022-04-19 18:42 ` Tom Rini
     [not found]   ` <HK0PR03MB2994FC1EF668377F8AE8C421C1F79@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-04-22  8:45     ` Rick Chen
2022-04-22 12:14       ` Tom Rini [this message]
2022-04-25  0:45         ` Rick Chen
2022-04-25 22:49 ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2022-03-02  7:42 Alan Kao
2022-03-02  7:50 ` Arnd Bergmann
2022-03-07 12:59   ` Arnd Bergmann
2022-03-02  6:52 Alan Kao

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=20220422121408.GY3045430@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=rick@andestech.com \
    --cc=rickchen36@gmail.com \
    --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.