mbox series

[v2,0/2] nuvoton,wpcm450-fiu binding example fixes

Message ID 20221129102225.3598044-1-j.neuschaefer@gmx.net
Headers show
Series nuvoton,wpcm450-fiu binding example fixes | expand

Message

J. Neuschäfer Nov. 29, 2022, 10:22 a.m. UTC
My recently merged nuvoton,wpcm450-fiu DT binding caused some
dt_binding_check issues in linux-next. This series attempts to fix them
before the breakage spreads any further.

Thanks to Rob Herring for running his dt_binding_check bot, and Conor
Dooley who notified me that the issue has reached linux-next.

v2:
- Some commit message improvements, as suggested by Krzysztof Kozlowski

Jonathan Neuschäfer (2):
  spi: dt-bindings: nuvoton,wpcm450-fiu: Fix error in example (bogus
    include)
  spi: dt-bindings: nuvoton,wpcm450-fiu: Fix warning in example (missing
    reg property)

 .../devicetree/bindings/spi/nuvoton,wpcm450-fiu.yaml          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--
2.35.1

Comments

Mark Brown Nov. 29, 2022, 1:11 p.m. UTC | #1
On Tue, 29 Nov 2022 11:22:23 +0100, Jonathan Neuschäfer wrote:
> My recently merged nuvoton,wpcm450-fiu DT binding caused some
> dt_binding_check issues in linux-next. This series attempts to fix them
> before the breakage spreads any further.
> 
> Thanks to Rob Herring for running his dt_binding_check bot, and Conor
> Dooley who notified me that the issue has reached linux-next.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: dt-bindings: nuvoton,wpcm450-fiu: Fix error in example (bogus include)
      commit: 1e2872f5912fbc87a00d00d49af98e428f4ff8b7
[2/2] spi: dt-bindings: nuvoton,wpcm450-fiu: Fix warning in example (missing reg property)
      commit: c771b4eabd6a52afff0b6f01c361a9d04fa8cd9d

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