From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> To: linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org> Cc: "Conor Dooley" <conor.dooley@microchip.com>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>, openbmc@lists.ozlabs.org, "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>, "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Subject: [PATCH v2 0/2] nuvoton,wpcm450-fiu binding example fixes Date: Tue, 29 Nov 2022 11:22:23 +0100 [thread overview] Message-ID: <20221129102225.3598044-1-j.neuschaefer@gmx.net> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> To: linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org> Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org, "Conor Dooley" <conor.dooley@microchip.com>, linux-kernel@vger.kernel.org, "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>, "Rob Herring" <robh+dt@kernel.org>, "Jonathan Neuschäfer" <j.neuschaefer@gmx.net> Subject: [PATCH v2 0/2] nuvoton,wpcm450-fiu binding example fixes Date: Tue, 29 Nov 2022 11:22:23 +0100 [thread overview] Message-ID: <20221129102225.3598044-1-j.neuschaefer@gmx.net> (raw) 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
next reply other threads:[~2022-11-29 10:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 10:22 Jonathan Neuschäfer [this message] 2022-11-29 10:22 ` [PATCH v2 0/2] nuvoton,wpcm450-fiu binding example fixes Jonathan Neuschäfer 2022-11-29 10:22 ` [PATCH v2 1/2] spi: dt-bindings: nuvoton,wpcm450-fiu: Fix error in example (bogus include) Jonathan Neuschäfer 2022-11-29 10:22 ` Jonathan Neuschäfer 2022-11-29 10:22 ` [PATCH v2 2/2] spi: dt-bindings: nuvoton,wpcm450-fiu: Fix warning in example (missing reg property) Jonathan Neuschäfer 2022-11-29 10:22 ` Jonathan Neuschäfer 2022-11-30 18:11 ` Geert Uytterhoeven 2022-11-30 18:11 ` Geert Uytterhoeven 2022-11-29 13:11 ` [PATCH v2 0/2] nuvoton,wpcm450-fiu binding example fixes Mark Brown
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20221129102225.3598044-1-j.neuschaefer@gmx.net \ --to=j.neuschaefer@gmx.net \ --cc=broonie@kernel.org \ --cc=conor.dooley@microchip.com \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=openbmc@lists.ozlabs.org \ --cc=robh+dt@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.