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

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: <167629820305.2707397.8230990509140378773.b4-ty@kernel.org>
Date:   Mon, 13 Feb 2023 14:23:23 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Linux SPI List <linux-spi@...r.kernel.org>,
        Broadcom Kernel List <bcm-kernel-feedback-list@...adcom.com>,
        William Zhang <william.zhang@...adcom.com>
Cc:     anand.gore@...adcom.com, dan.beygelman@...adcom.com,
        joel.peshkin@...adcom.com, dregan@...l.com, f.fainelli@...il.com,
        kursad.oney@...adcom.com, tomer.yacoby@...adcom.com,
        jonas.gorski@...il.com, kernel test robot <lkp@...el.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove file reference for Broadcom
 Broadband SoC HS SPI driver entry

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@...el.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