linux-kernel - Re: [PATCH] MAINTAINERS: rectify entry for ARM/HPE GXP ARCHITECTURE

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: <165970564600.1040888.14372925011980629843.b4-ty@kernel.org>
Date:   Fri, 05 Aug 2022 14:20:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Nick Hawkins <nick.hawkins@....com>,
        Jean-Marie Verdun <verdun@....com>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-spi@...r.kernel.org
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify entry for ARM/HPE GXP ARCHITECTURE

On Thu, 4 Aug 2022 18:18:23 +0200, Lukas Bulwahn wrote:
> Commit 8cc35b86546d ("spi: dt-bindings: add documentation for
> hpe,gxp-spifi") adds the spi dt-binding file hpe,gxp-spifi.yaml and commit
> a1848b0fa251 ("MAINTAINERS: add spi support to GXP") adds a file entry
> hpe,gxp-spi.yaml in ARM/HPE GXP ARCHITECTURE. Note the different file name.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> [...]

Applied to

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

Thanks!

[1/1] MAINTAINERS: rectify entry for ARM/HPE GXP ARCHITECTURE
      commit: 706864c99e0e2d301da9e749395909bc309c50a0

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