mbox series

[v2,0/2] spi: intel: PCI driver housekeeping

Message ID 20230201205455.550308-1-mauro.lima@eclypsium.com (mailing list archive)
Headers show
Series spi: intel: PCI driver housekeeping | expand

Message

Mauro Lima Feb. 1, 2023, 8:54 p.m. UTC 
Found some controllers' private data that were wrong according
to the documentation. Also, the number of Protected Regions from 
Broxton types was changed.
The second patch adds more Device IDs to the module table.
Probably good candidates to stable?

Changes since v1:
	* Change BXT to Broxton in commit message
	* Sort new Device IDs by hex value in the driver's module table
	* Add ack from Mika Westerberg to the first patch
	Link: https://lore.kernel.org/r/20230201050455.505135-1-mauro.lima@eclypsium.com

Mauro Lima (2):
  spi: intel: Fix device private data and PR_NUM for Broxton controllers
  spi: intel: Add support for controllers

 drivers/spi/spi-intel-pci.c | 13 ++++++++-----
 drivers/spi/spi-intel.c     |  2 +-
 2 files changed, 9 insertions(+), 6 deletions(-)

Comments

Mark Brown Feb. 2, 2023, 2:59 p.m. UTC | #1 
On Wed, 01 Feb 2023 17:54:53 -0300, Mauro Lima wrote:
> Found some controllers' private data that were wrong according
> to the documentation. Also, the number of Protected Regions from
> Broxton types was changed.
> The second patch adds more Device IDs to the module table.
> Probably good candidates to stable?
> 
> Changes since v1:
> 	* Change BXT to Broxton in commit message
> 	* Sort new Device IDs by hex value in the driver's module table
> 	* Add ack from Mika Westerberg to the first patch
> 	Link: https://lore.kernel.org/r/20230201050455.505135-1-mauro.lima@eclypsium.com
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: intel: Fix device private data and PR_NUM for Broxton controllers
      commit: b4c58d540777124f31ab0cb37a14c6573438d381
[2/2] spi: intel: Add support for controllers
      commit: 7c62a2279b9e88f2cbfa3b92dc49c8b7806c56f8

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