Remove Intel Thunder Bay SOC support

[PATCH v1 0/2] Remove Intel Thunder Bay SOC support

Posted by nandhini.srikandan@intel.com 2 years ago

From: Nandhini Srikandan <nandhini.srikandan@intel.com>

This patch set removes Intel Thunder Bay specific code as the product              
got cancelled and there are no end customers.                                      
                                                                                   
Patch 1: Remove Intel Thunder Bay spi dw binding specific code.                    
Patch 2: Remove Intel Thunder Bay spi dw binding Documentation.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Nandhini Srikandan (2):
  spi: dw: Remove Intel Thunder Bay SOC support
  spi: dw: Remove Intel Thunder Bay SOC support

 Documentation/devicetree/bindings/spi/snps,dw-apb-ssi.yaml | 2 --
 drivers/spi/spi-dw-mmio.c                                  | 1 -
 2 files changed, 3 deletions(-)

-- 
2.17.1

Re: [PATCH v1 0/2] Remove Intel Thunder Bay SOC support

Posted by Mark Brown 2 years ago

On Wed, 13 Dec 2023 14:08:34 +0800, nandhini.srikandan@intel.com wrote:
> This patch set removes Intel Thunder Bay specific code as the product
> got cancelled and there are no end customers.
> 
> Patch 1: Remove Intel Thunder Bay spi dw binding specific code.
> Patch 2: Remove Intel Thunder Bay spi dw binding Documentation.
> 
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: dw: Remove Intel Thunder Bay SOC support
      commit: e1fca6957f1966cb6e75cdc354f4bcaed230a454
[2/2] spi: dw: Remove Intel Thunder Bay SOC support
      commit: e1fca6957f1966cb6e75cdc354f4bcaed230a454

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