linux-kernel - Re: [PATCH 2/3] spi: ppc4xx: Fix fallout from rename in struct spi

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 27 Feb 2024 12:50:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: Rob Herring <robh@...nel.org>, kernel test robot <lkp@...el.com>,
	Stephen Warren <swarren@...dotorg.org>,
	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	H Hartley Sweeten <hsweeten@...ionengravers.com>,
	kernel@...gutronix.de,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH 2/3] spi: ppc4xx: Fix fallout from rename in struct
 spi_bitbang

On Tue, Feb 27, 2024 at 08:23:06AM +0100, Uwe Kleine-König wrote:

> Assuming we don't want to have this problem in v6.8, I suggest to revert
> de4af897ddf2 and reapply it on top of your next branch.

BTW the issue here is that you sent this without comment in the middle
of a series of fixes the other two of which *do* apply to mainline,
ideally it would have just been sent separately since it needs to go
separately but if you *are* going to send a single series like this
things that are -next only should go after any fixes that are for
mainline.  My automation does look at where fixes are targeted this
catches it out.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)