linux-kernel - Re: [PATCH v2 1/1] spi: ppc4xx: Revert "handle irq_of_parse_and

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] [day] [month] [year] [list]

Message-Id: <172530105989.141806.10633264451123682243.b4-ty@kernel.org>
Date: Mon, 02 Sep 2024 19:17:39 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v2 1/1] spi: ppc4xx: Revert "handle
 irq_of_parse_and_map() errors"

On Mon, 02 Sep 2024 13:28:26 +0300, Andy Shevchenko wrote:
> The commit had been applied twice as
>   0f245463b01e ("spi: ppc4xx: handle irq_of_parse_and_map() errors")
> and
>   f1011ba20b83 ("spi: ppc4xx: handle irq_of_parse_and_map() errors")
> 
> This reverts commit f1011ba20b83da3ee70dcb4a6d9d282a718916fa.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: ppc4xx: Revert "handle irq_of_parse_and_map() errors"
      commit: 7f9f8c5939b1d729470a15480a4ffb0512d39d3a

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