From: patchwork-bot+chrome-platform@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, bleung@chromium.org, groeck@chromium.org,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, gregkh@linuxfoundation.org,
pmalani@chromium.org, waynec@nvidia.com,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: usb: connector: disallow additional properties
Date: Mon, 11 Sep 2023 04:49:00 +0000 [thread overview]
Message-ID: <169440774016.22573.10427035970076911833.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725102325.76336-1-krzysztof.kozlowski@linaro.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Rob Herring <robh@kernel.org>:
On Tue, 25 Jul 2023 12:23:25 +0200 you wrote:
> USB connector bindings is complete, thus no additional properties should
> be allowed. Add missing 'reg' property and change additionalProperties
> to false, so the schema will check for anything not unexpected. This
> also allows to drop the 'reg' from other bindings referencing the
> usb-connector.yaml and make it required.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> [...]
Here is the summary with links:
- [v2] dt-bindings: usb: connector: disallow additional properties
https://git.kernel.org/chrome-platform/c/e251a4e28a27
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-09-11 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:23 [PATCH v2] dt-bindings: usb: connector: disallow additional properties Krzysztof Kozlowski
2023-07-25 10:35 ` Krzysztof Kozlowski
2023-07-27 17:09 ` Rob Herring
2023-09-11 4:31 ` patchwork-bot+chrome-platform
2023-09-11 4:49 ` patchwork-bot+chrome-platform [this message]
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=169440774016.22573.10427035970076911833.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=robh+dt@kernel.org \
--cc=waynec@nvidia.com \
/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: link
Be 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.