From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: "open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] MIPS: TXX9: Remove rbtx4938 board support
Date: Wed, 1 Dec 2021 13:42:01 +0100 [thread overview]
Message-ID: <CAMuHMdUqKcnpDeKFaKs4sx_9UpeQYyfVrSDyqYf6MxFbdr64Gg@mail.gmail.com> (raw)
In-Reply-To: <20211130164558.85584-1-tsbogend@alpha.franken.de>
Hi Thomas,
On Tue, Nov 30, 2021 at 5:46 PM Thomas Bogendoerfer
<tsbogend@alpha.franken.de> wrote:
> No active MIPS user own this board, so let's remove it.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Thanks for your patch!
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
My rbtx4927 still works fine afterwards, so
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-12-01 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 16:45 [PATCH 1/3] MIPS: TXX9: Remove rbtx4938 board support Thomas Bogendoerfer
2021-11-30 16:45 ` [PATCH 2/3] MIPS: TXX9: Remove rbtx4939 " Thomas Bogendoerfer
2021-12-01 13:04 ` Geert Uytterhoeven
2022-01-02 13:27 ` Thomas Bogendoerfer
2021-11-30 16:45 ` [PATCH 3/3] MIPS: TXX9: Remove TX4939 SoC support Thomas Bogendoerfer
2021-12-01 13:06 ` Geert Uytterhoeven
2022-01-02 13:27 ` Thomas Bogendoerfer
2021-12-01 12:42 ` Geert Uytterhoeven [this message]
2021-12-09 9:30 ` [PATCH 1/3] MIPS: TXX9: Remove rbtx4938 board support Thomas Bogendoerfer
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=CAMuHMdUqKcnpDeKFaKs4sx_9UpeQYyfVrSDyqYf6MxFbdr64Gg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).