[PATCH] MAINTAINERS: Remove file reference for Broadcom Broadband SoC HS SPI driver entry

[PATCH] MAINTAINERS: Remove file reference for Broadcom Broadband SoC HS SPI driver entry

[William Zhang]

brcm,bcm63xx-hsspi-peripheral-props.yaml is not in use at least for now.
Remove it from the maintainer entry.

Fixes: 80323599e33f ("MAINTAINERS: Add entry for Broadcom Broadband SoC HS SPI drivers")
Reported-by: kernel test robot <lkp@intel.com>
https://lore.kernel.org/oe-kbuild-all/202302121840.GtduUT37-lkp@intel.com/

Signed-off-by: William Zhang <william.zhang@broadcom.com>

---

 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index c6a2c3175ea3..df1c71ca1a69 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4306,7 +4306,6 @@ M:	Jonas Gorski <jonas.gorski@gmail.com>
 R:	Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
 L:	linux-spi@vger.kernel.org
 S:	Maintained
-F:	Documentation/devicetree/bindings/spi/brcm,bcm63xx-hsspi-peripheral-props.yaml
 F:	Documentation/devicetree/bindings/spi/brcm,bcm63xx-hsspi.yaml
 F:	drivers/spi/spi-bcm63xx-hsspi.c
 F:	drivers/spi/spi-bcmbca-hsspi.c
-- 
2.37.3

Re: [PATCH] MAINTAINERS: Remove file reference for Broadcom Broadband SoC HS SPI driver entry

[Mark Brown]

On Sun, 12 Feb 2023 12:50:54 -0800, William Zhang wrote:
> brcm,bcm63xx-hsspi-peripheral-props.yaml is not in use at least for now.
> Remove it from the maintainer entry.
> 
> Fixes: 80323599e33f ("MAINTAINERS: Add entry for Broadcom Broadband SoC HS SPI drivers")
> Reported-by: kernel test robot <lkp@intel.com>
> https://lore.kernel.org/oe-kbuild-all/202302121840.GtduUT37-lkp@intel.com/
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] MAINTAINERS: Remove file reference for Broadcom Broadband SoC HS SPI driver entry
      commit: 937ca916bf4de427242fb78105a0089af0dd43b3

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