linux-kernel - Re: [PATCH v1 1/1] spi: sc18is602: Switch to generic firmware properties and drop of_match

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: <173315826335.126887.7469821187723092456.b4-ty@kernel.org>
Date: Mon, 02 Dec 2024 16:51:03 +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 1/1] spi: sc18is602: Switch to generic firmware
 properties and drop of_match_ptr()

On Thu, 14 Nov 2024 22:50:51 +0200, Andy Shevchenko wrote:
> This enables using the driver with other firmware types such as ACPI
> via PRP0001.
> 
> Also part of a general attempt to move drivers over to generic properties
> to avoid opportunities for cut and paste.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: sc18is602: Switch to generic firmware properties and drop of_match_ptr()
      commit: 2c55f67c3a71cf57665294a02f258625c1da9385

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