linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org
Cc: geert@linux-m68k.org
Subject: Re: [PATCH 2/3] MIPS: TXX9: Remove rbtx4939 board support
Date: Sun, 2 Jan 2022 14:27:33 +0100	[thread overview]
Message-ID: <20220102132733.GC3468@alpha.franken.de> (raw)
In-Reply-To: <20211130164558.85584-2-tsbogend@alpha.franken.de>

On Tue, Nov 30, 2021 at 05:45:55PM +0100, Thomas Bogendoerfer wrote:
> No active MIPS user own this board, so let's remove it.
> 
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
>  arch/mips/configs/rbtx49xx_defconfig          |   2 -
>  .../include/asm/mach-tx49xx/mangle-port.h     |   8 -
>  arch/mips/include/asm/txx9/boards.h           |   3 -
>  arch/mips/include/asm/txx9/rbtx4939.h         | 142 -----
>  arch/mips/txx9/Kconfig                        |  12 -
>  arch/mips/txx9/Makefile                       |   1 -
>  arch/mips/txx9/generic/7segled.c              | 123 ----
>  arch/mips/txx9/generic/Makefile               |   1 -
>  arch/mips/txx9/generic/setup.c                |  20 -
>  arch/mips/txx9/rbtx4939/Makefile              |   2 -
>  arch/mips/txx9/rbtx4939/irq.c                 |  95 ---
>  arch/mips/txx9/rbtx4939/prom.c                |  29 -
>  arch/mips/txx9/rbtx4939/setup.c               | 554 ------------------
>  drivers/mtd/maps/Kconfig                      |   6 -
>  drivers/mtd/maps/Makefile                     |   1 -
>  drivers/mtd/maps/rbtx4939-flash.c             | 133 -----
>  16 files changed, 1132 deletions(-)
>  delete mode 100644 arch/mips/include/asm/txx9/rbtx4939.h
>  delete mode 100644 arch/mips/txx9/generic/7segled.c
>  delete mode 100644 arch/mips/txx9/rbtx4939/Makefile
>  delete mode 100644 arch/mips/txx9/rbtx4939/irq.c
>  delete mode 100644 arch/mips/txx9/rbtx4939/prom.c
>  delete mode 100644 arch/mips/txx9/rbtx4939/setup.c
>  delete mode 100644 drivers/mtd/maps/rbtx4939-flash.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 ]

  parent reply	other threads:[~2022-01-02 13:33 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 [this message]
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 ` [PATCH 1/3] MIPS: TXX9: Remove rbtx4938 board support Geert Uytterhoeven
2021-12-09  9:30 ` 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=20220102132733.GC3468@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=geert@linux-m68k.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=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).