From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH] dt-bindings: display/msm/dsi-phy: drop unused allOf clauses
Date: Fri, 13 Jan 2023 15:08:07 -0600 [thread overview]
Message-ID: <20230113210807.GA2901424-robh@kernel.org> (raw)
In-Reply-To: <20230113063351.24131-1-dmitry.baryshkov@linaro.org>
On Fri, Jan 13, 2023 at 08:33:51AM +0200, Dmitry Baryshkov wrote:
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> .../devicetree/bindings/display/msm/dsi-phy-10nm.yaml | 3 +--
> .../devicetree/bindings/display/msm/dsi-phy-14nm.yaml | 3 +--
> .../devicetree/bindings/display/msm/dsi-phy-20nm.yaml | 3 +--
> .../devicetree/bindings/display/msm/dsi-phy-28nm.yaml | 3 +--
> Documentation/devicetree/bindings/display/msm/dsi-phy-7nm.yaml | 3 +--
> 5 files changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/dsi-phy-10nm.yaml b/Documentation/devicetree/bindings/display/msm/dsi-phy-10nm.yaml
> index 3ec466c3ab38..71702151bafa 100644
> --- a/Documentation/devicetree/bindings/display/msm/dsi-phy-10nm.yaml
> +++ b/Documentation/devicetree/bindings/display/msm/dsi-phy-10nm.yaml
> @@ -9,8 +9,7 @@ title: Qualcomm Display DSI 10nm PHY
> maintainers:
> - Krishna Manikandan <quic_mkrishn@quicinc.com>
>
> -allOf:
> - - $ref: dsi-phy-common.yaml#
> +$ref: dsi-phy-common.yaml#
Convention is how it was. Partly this is legacy because earlier versions
of json-schema required the 'allOf' form or everything in addition to
the $ref would be ignored. I left these thinking more than 1 $ref here
might be common. But probably more common is a $ref and if/then schemas
and I'd somewhat rather keep $ref at the top and if/then schemas at the
bottom. So maybe this is the right direction.
I don't really care to define one way or the other if we can't enforce
it in the meta-schema. I don't need more nits to look for in reviews.
Adding a check (i.e. allOf must have 2 or more entries) would be quite
invasive and wouldn't allow having 1 entry when we expect a 2nd entry
soonish.
Rob
next prev parent reply other threads:[~2023-01-13 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 6:33 [PATCH] dt-bindings: display/msm/dsi-phy: drop unused allOf clauses Dmitry Baryshkov
2023-01-13 21:08 ` Rob Herring [this message]
2023-01-13 21:14 ` Dmitry Baryshkov
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=20230113210807.GA2901424-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox