From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-crypto@vger.kernel.org, linux-mtd@lists.infradead.org
Cc: geert@linux-m68k.org
Subject: Re: [PATCH 3/3] MIPS: TXX9: Remove TX4939 SoC support
Date: Sun, 2 Jan 2022 14:27:57 +0100 [thread overview]
Message-ID: <20220102132757.GD3468@alpha.franken.de> (raw)
In-Reply-To: <20211130164558.85584-3-tsbogend@alpha.franken.de>
On Tue, Nov 30, 2021 at 05:45:56PM +0100, Thomas Bogendoerfer wrote:
> After removal of RBTX4939 board support remove code for the TX4939 SoC.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/pci/Makefile | 1 -
> arch/mips/pci/pci-tx4939.c | 107 -----
> arch/mips/txx9/Kconfig | 8 -
> arch/mips/txx9/generic/Makefile | 1 -
> arch/mips/txx9/generic/irq_tx4939.c | 216 ----------
> arch/mips/txx9/generic/setup_tx4939.c | 568 --------------------------
> drivers/char/hw_random/Kconfig | 13 -
> drivers/char/hw_random/Makefile | 1 -
> drivers/char/hw_random/tx4939-rng.c | 157 -------
> drivers/mtd/nand/raw/Kconfig | 2 +-
> 10 files changed, 1 insertion(+), 1073 deletions(-)
> delete mode 100644 arch/mips/pci/pci-tx4939.c
> delete mode 100644 arch/mips/txx9/generic/irq_tx4939.c
> delete mode 100644 arch/mips/txx9/generic/setup_tx4939.c
> delete mode 100644 drivers/char/hw_random/tx4939-rng.c
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-01-02 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211130164558.85584-1-tsbogend@alpha.franken.de>
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 [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=20220102132757.GD3468@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mpm@selenic.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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).