linux-kernel - Re: [PATCH v1 0/2] spi: Unify and simplify fwnode related checks

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 for Android: free password hash cracker in your pocket

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

Message-Id: <173385393085.127025.726656879315481364.b4-ty@kernel.org>
Date: Tue, 10 Dec 2024 18:05:30 +0000
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 v1 0/2] spi: Unify and simplify fwnode related checks

On Sun, 08 Dec 2024 18:03:15 +0200, Andy Shevchenko wrote:
> A couple of cleanups on top of recently added change.
> 
> Andy Shevchenko (2):
>   spi: Unify firmware node type checks
>   spi: Deduplicate deferred probe checks in spi_probe()
> 
> drivers/spi/spi.c | 41 ++++++++++++++++++-----------------------
>  1 file changed, 18 insertions(+), 23 deletions(-)
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: Unify firmware node type checks
      commit: b6ffe0e6147915fe3d31705e14dfbbecb724fb81
[2/2] spi: Deduplicate deferred probe checks in spi_probe()
      commit: 0020c9d2d572b49c55b2e1fabe6f6687e11a3ced

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