[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yu0I1sxjC3SU5y3x@sirena.org.uk>
Date: Fri, 5 Aug 2022 13:11:02 +0100
From: Mark Brown <broonie@...nel.org>
To: Conor.Dooley@...rochip.com
Cc: Nagasuresh.Relli@...rochip.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Valentina.FernandezAlanis@...rochip.com
Subject: Re: [PATCH v3 4/4] MAINTAINERS: add qspi to Polarfire SoC entry
On Fri, Aug 05, 2022 at 12:07:57PM +0000, Conor.Dooley@...rochip.com wrote:
> On 05/08/2022 12:05, Mark Brown wrote:
> >> +++ b/MAINTAINERS
> >> @@ -17146,6 +17146,7 @@ S: Supported
> >> F: arch/riscv/boot/dts/microchip/
> >> F: drivers/mailbox/mailbox-mpfs.c
> >> F: drivers/soc/microchip/
> >> +F: drivers/spi/spi-microchip-core-qspi.c
> >> F: drivers/spi/spi-microchip-core.c
> >> F: include/soc/microchip/mpfs.h
> > You should also add a pattern for the DT binding here.
> All of the bindings for the platform should have entries then
> right? I'll send a separate patch adding all of the missing
> bindings. I have a deferred change to the entry that needs to
> be sent to Arnd anyway so I can queue the two together.
> Nothing to be gained by waiting until this driver lands in 6.1+
> to have MAINTAINERS coverage of the bindings :)
Yes, it's better if everything has coverage - that way the platform
maintainers are more likely to see any changes that are needed for the
bindings. Sending as part of a bigger patch adding the rest sounds
good.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists