linux-kernel - Re: [PATCH] spi: spi_amd: Add PCI-based driver for AMD HID2 SPI controller

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: <174404254940.780717.3439023568635859213.b4-ty@kernel.org>
Date: Mon, 07 Apr 2025 17:15:49 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org, 
 Raju Rangoju <Raju.Rangoju@....com>
Cc: Krishnamoorthi M <krishnamoorthi.m@....com>, 
 Akshata MukundShetty <akshata.mukundshetty@....com>
Subject: Re: [PATCH] spi: spi_amd: Add PCI-based driver for AMD HID2 SPI
 controller

On Wed, 02 Apr 2025 17:45:14 +0530, Raju Rangoju wrote:
> Register a new driver(spi_amd_pci) for the HID2 SPI controller using the
> PCI ID of the LPC bridge device.
> 
> Add a new common probe function in spi_amd driver to encapsulate the
> code required for registering the controller driver. This function will be
> utilized by both the existing ACPI driver and the newly introduced
> PCI-based driver for the HID2 SPI controller. The MMIO register base
> address of the HID2 SPI controller can be obtained from the PCI LPC bridge
> registers.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi_amd: Add PCI-based driver for AMD HID2 SPI controller
      commit: b644c2776652671256edcd7a8e71161e212b59ac

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