[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160994509314.52132.9683741232298303961.b4-ty@kernel.org>
Date: Wed, 06 Jan 2021 14:58:13 +0000
From: Mark Brown <broonie@...nel.org>
To: Takashi Iwai <tiwai@...e.com>, linux-kernel@...r.kernel.org,
linux-mtd@...ts.infradead.org, Guenter Roeck <linux@...ck-us.net>,
Dan Williams <dan.j.williams@...el.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
linux-rtc@...r.kernel.org,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-spi@...r.kernel.org, linux-ide@...r.kernel.org,
Jaroslav Kysela <perex@...ex.cz>, linux-crypto@...r.kernel.org,
linux-watchdog@...r.kernel.org,
Richard Weinberger <richard@....at>, dmaengine@...r.kernel.org,
Liam Girdwood <lgirdwood@...il.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Jakub Kicinski <kuba@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
netdev@...r.kernel.org, Miquel Raynal <miquel.raynal@...tlin.com>,
Matt Mackall <mpm@...enic.com>, alsa-devel@...a-project.org,
linux-mips@...r.kernel.org, Vignesh Raghavendra <vigneshr@...com>,
Vinod Koul <vkoul@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: (subset) [PATCH 00/10] Remove support for TX49xx
On Tue, 5 Jan 2021 15:02:45 +0100, Thomas Bogendoerfer wrote:
> I couldn't find any buyable product other than reference boards using
> TX49xx CPUs. And since nobody showed interest in keeping support for
> it, it's time to remove it.
>
> I've split up the removal into seperate parts for different maintainers.
> So if the patch fits your needs, please take it via your tree or
> give me an ack so I can apply them the mips-next tree.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[10/10] ASoC: txx9: Remove driver
commit: a8644292ea46064f990e4a3c4585bdb294c0d89a
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
Powered by blists - more mailing lists