[0/3] spi: ppc4xx: Various fixes

Message

Uwe Kleine-König Feb. 10, 2024, 4:40 p.m. UTC

Hello,

this series fixes three problems of the spi-ppc4xx driver. One of them
was introduced by myself, the other two are already older. I guess they
were unhandled before because the driver isn't enabled in any
allmodconfig build.

Now that I have this series, I found the first patch to be a duplicate
of
https://lore.kernel.org/linux-spi/[e-mail]/
. Mark claimed to have applied this patch to his for-next branch, but
it's not included there yet. So I kept my version of it to please the
build bots. (Also my patch has a Fixes: line, which Christian's doesn't.
Up to Mark what to do with that.)

Best regards
Uwe

Uwe Kleine-König (3):
  spi: ppc4xx: Fix fallout from include cleanup
  spi: ppc4xx: Fix fallout from rename in struct spi_bitbang
  spi: ppc4xx: Drop write-only variable

 drivers/spi/spi-ppc4xx.c | 20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)

base-commit: 65b3e71d024d553764e67e5916a41675afd0d142

Comments

Mark Brown Feb. 12, 2024, 1:02 a.m. UTC | #1

On Sat, 10 Feb 2024 17:40:05 +0100, Uwe Kleine-König wrote:
> this series fixes three problems of the spi-ppc4xx driver. One of them
> was introduced by myself, the other two are already older. I guess they
> were unhandled before because the driver isn't enabled in any
> allmodconfig build.
> 
> Now that I have this series, I found the first patch to be a duplicate
> of
> https://lore.kernel.org/linux-spi/[e-mail]/
> . Mark claimed to have applied this patch to his for-next branch, but
> it's not included there yet. So I kept my version of it to please the
> build bots. (Also my patch has a Fixes: line, which Christian's doesn't.
> Up to Mark what to do with that.)
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] spi: ppc4xx: Fix fallout from include cleanup
      commit: 6f98e44984d5eff599906c0376c027df985bf38b
[2/3] spi: ppc4xx: Fix fallout from rename in struct spi_bitbang
      commit: de4af897ddf242aea18ee90d3ad2e21b4e64359c
[3/3] spi: ppc4xx: Drop write-only variable
      commit: b3aa619a8b4706f35cb62f780c14e68796b37f3f

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

Mark Brown Feb. 27, 2024, 6:20 p.m. UTC | #2

On Sat, 10 Feb 2024 17:40:05 +0100, Uwe Kleine-König wrote:
> this series fixes three problems of the spi-ppc4xx driver. One of them
> was introduced by myself, the other two are already older. I guess they
> were unhandled before because the driver isn't enabled in any
> allmodconfig build.
> 
> Now that I have this series, I found the first patch to be a duplicate
> of
> https://lore.kernel.org/linux-spi/[e-mail]/
> . Mark claimed to have applied this patch to his for-next branch, but
> it's not included there yet. So I kept my version of it to please the
> build bots. (Also my patch has a Fixes: line, which Christian's doesn't.
> Up to Mark what to do with that.)
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[2/3] spi: ppc4xx: Fix fallout from rename in struct spi_bitbang
      commit: d748b48eeba8e1a10c822109252b75ca30288ca0

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