lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 05 Jan 2021 16:08:10 +0000 From: Mark Brown <broonie@...nel.org> To: linux-rtc@...r.kernel.org, Matt Mackall <mpm@...enic.com>, linux-mtd@...ts.infradead.org, linux-crypto@...r.kernel.org, netdev@...r.kernel.org, alsa-devel@...a-project.org, dmaengine@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>, Wim Van Sebroeck <wim@...ux-watchdog.org>, Miquel Raynal <miquel.raynal@...tlin.com>, Richard Weinberger <richard@....at>, Dan Williams <dan.j.williams@...el.com>, "David S. Miller" <davem@...emloft.net>, linux-mips@...r.kernel.org, Takashi Iwai <tiwai@...e.com>, Alessandro Zummo <a.zummo@...ertech.it>, Jaroslav Kysela <perex@...ex.cz>, Vignesh Raghavendra <vigneshr@...com>, Jakub Kicinski <kuba@...nel.org>, linux-watchdog@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>, Alexandre Belloni <alexandre.belloni@...tlin.com>, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org, Thomas Bogendoerfer <tsbogend@...ha.franken.de>, Vinod Koul <vkoul@...nel.org>, Liam Girdwood <lgirdwood@...il.com>, linux-spi@...r.kernel.org 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/spi.git for-next Thanks! [04/10] spi: txx9: Remove driver commit: 74523a5dae0c96d6503fe72da66ee37fd23eb8f5 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