From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: geert@linux-m68k.org
Cc: tsbogend@alpha.franken.de, mpm@selenic.com,
herbert@gondor.apana.org.au, dan.j.williams@intel.com,
vkoul@kernel.org, davem@davemloft.net, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, kuba@kernel.org,
a.zummo@towertech.it, alexandre.belloni@bootlin.com,
broonie@kernel.org, wim@linux-watchdog.org, linux@roeck-us.net,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
linux-ide@vger.kernel.org, linux-mtd@lists.infradead.org,
netdev@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-spi@vger.kernel.org, linux-watchdog@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 00/10] Remove support for TX49xx
Date: Thu, 07 Jan 2021 10:17:29 +0900 (JST) [thread overview]
Message-ID: <20210107.101729.1936921832901251107.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <CAMuHMdV86BES7dmWr-7j1jbtoSy0bH1J0e5W41p8evagi0Nqcw@mail.gmail.com>
On Wed, 6 Jan 2021 21:41:24 +0100, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> > Is that sufficient to keep it?
>>
>> for me it is. But now we probaly need some reverts then...
>
> Indeed. Fortunately not all of it, as some removals were TX4938-only.
These patches should not break RBTX4927:
net: tc35815: Drop support for TX49XX boards
spi: txx9: Remove driver
mtd: Remove drivers used by TX49xx
char: hw_random: Remove tx4939 driver
rtc: tx4939: Remove driver
ide: tx4938ide: Remove driver
And these patches just break audio-support only.
dma: tx49 removal
ASoC: txx9: Remove driver
I think dma and ASoC drivers are hard to maintain now, and can be
dropped for basic support for RBTX4927.
(TX39 boards does not have audio-support, so dma txx9 driver can be
dropped too)
---
Atsushi Nemoto
WARNING: multiple messages have this Message-ID (diff)
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: geert@linux-m68k.org
Cc: alexandre.belloni@bootlin.com, vigneshr@ti.com,
lgirdwood@gmail.com, alsa-devel@alsa-project.org, tiwai@suse.com,
linux-ide@vger.kernel.org, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, linux-spi@vger.kernel.org,
linux-rtc@vger.kernel.org, wim@linux-watchdog.org,
herbert@gondor.apana.org.au, richard@nod.at, kuba@kernel.org,
linux@roeck-us.net, linux-watchdog@vger.kernel.org,
broonie@kernel.org, mpm@selenic.com, dan.j.williams@intel.com,
perex@perex.cz, a.zummo@towertech.it, tsbogend@alpha.franken.de,
netdev@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, vkoul@kernel.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH 00/10] Remove support for TX49xx
Date: Thu, 07 Jan 2021 10:17:29 +0900 (JST) [thread overview]
Message-ID: <20210107.101729.1936921832901251107.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <CAMuHMdV86BES7dmWr-7j1jbtoSy0bH1J0e5W41p8evagi0Nqcw@mail.gmail.com>
On Wed, 6 Jan 2021 21:41:24 +0100, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> > Is that sufficient to keep it?
>>
>> for me it is. But now we probaly need some reverts then...
>
> Indeed. Fortunately not all of it, as some removals were TX4938-only.
These patches should not break RBTX4927:
net: tc35815: Drop support for TX49XX boards
spi: txx9: Remove driver
mtd: Remove drivers used by TX49xx
char: hw_random: Remove tx4939 driver
rtc: tx4939: Remove driver
ide: tx4938ide: Remove driver
And these patches just break audio-support only.
dma: tx49 removal
ASoC: txx9: Remove driver
I think dma and ASoC drivers are hard to maintain now, and can be
dropped for basic support for RBTX4927.
(TX39 boards does not have audio-support, so dma txx9 driver can be
dropped too)
---
Atsushi Nemoto
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-01-07 1:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 14:02 [PATCH 00/10] Remove support for TX49xx Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 01/10] MIPS: TX49xx: Drop support Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:59 ` Guenter Roeck
2021-01-05 14:59 ` Guenter Roeck
2021-01-05 14:02 ` [PATCH 02/10] net: tc35815: Drop support for TX49XX boards Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 03/10] net: 8390: " Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 04/10] spi: txx9: Remove driver Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 05/10] dma: tx49 removal Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-06 6:18 ` Vinod Koul
2021-01-06 6:18 ` Vinod Koul
2021-01-06 6:18 ` Vinod Koul
2021-01-06 19:10 ` Joe Perches
2021-01-06 19:10 ` Joe Perches
2021-01-06 19:10 ` Joe Perches
2021-01-07 16:40 ` Thomas Bogendoerfer
2021-01-07 16:40 ` Thomas Bogendoerfer
2021-01-07 16:40 ` Thomas Bogendoerfer
2021-01-08 8:27 ` Vinod Koul
2021-01-08 8:27 ` Vinod Koul
2021-01-08 8:27 ` Vinod Koul
2021-01-05 14:02 ` [PATCH 06/10] mtd: Remove drivers used by TX49xx Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:06 ` Miquel Raynal
2021-01-05 14:06 ` Miquel Raynal
2021-01-05 14:06 ` Miquel Raynal
2021-01-05 14:02 ` [PATCH 07/10] char: hw_random: Remove tx4939 driver Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 08/10] rtc: tx4939: Remove driver Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 09/10] ide: tx4938ide: " Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 14:02 ` [PATCH 10/10] ASoC: txx9: " Thomas Bogendoerfer
2021-01-05 14:02 ` Thomas Bogendoerfer
2021-01-05 16:08 ` (subset) [PATCH 00/10] Remove support for TX49xx Mark Brown
2021-01-05 16:08 ` Mark Brown
2021-01-06 8:37 ` Geert Uytterhoeven
2021-01-06 8:37 ` Geert Uytterhoeven
2021-01-06 16:03 ` Atsushi Nemoto
2021-01-06 16:03 ` Atsushi Nemoto
2021-01-06 18:48 ` Thomas Bogendoerfer
2021-01-06 18:48 ` Thomas Bogendoerfer
2021-01-06 20:41 ` Geert Uytterhoeven
2021-01-06 20:41 ` Geert Uytterhoeven
2021-01-07 1:17 ` Atsushi Nemoto [this message]
2021-01-07 1:17 ` Atsushi Nemoto
2021-01-07 8:04 ` Geert Uytterhoeven
2021-01-07 8:04 ` Geert Uytterhoeven
2021-01-07 8:04 ` Geert Uytterhoeven
2021-01-06 14:58 ` (subset) " Mark Brown
2021-01-06 14:58 ` Mark Brown
2021-01-12 23:33 ` Alexandre Belloni
2021-01-12 23:33 ` Alexandre Belloni
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=20210107.101729.1936921832901251107.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=miquel.raynal@bootlin.com \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=perex@perex.cz \
--cc=richard@nod.at \
--cc=tiwai@suse.com \
--cc=tsbogend@alpha.franken.de \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
--cc=wim@linux-watchdog.org \
/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.