mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Taniya Das <quic_tdas@quicinc.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: (subset) [PATCH 1/2] dt-bindings: clock: qcom,sc7280-lpasscorecc: order properties to match convention
Date: Tue, 17 Dec 2024 10:38:52 -0600	[thread overview]
Message-ID: <173445353299.470882.2185588952896722099.b4-ty@kernel.org> (raw)
In-Reply-To: <20240817094605.27185-1-krzysztof.kozlowski@linaro.org>


On Sat, 17 Aug 2024 11:46:04 +0200, Krzysztof Kozlowski wrote:
> By convention we expect first "compatible", then "reg" and then rest.
> Order properties to match convention and what is in "required:" block.
> 
> 

Applied, thanks!

[1/2] dt-bindings: clock: qcom,sc7280-lpasscorecc: order properties to match convention
      commit: 2a5711c7dc6f20e132f99b13731952bdb3530acf
[2/2] dt-bindings: clock: qcom,sc7280-lpasscorecc: add top-level constraints
      commit: 9d40c5a698de6ba629f2abc8dd43b8a2db469307

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2024-12-17 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  9:46 Krzysztof Kozlowski
2024-08-17  9:46 ` [PATCH 2/2] dt-bindings: clock: qcom,sc7280-lpasscorecc: add top-level constraints Krzysztof Kozlowski
2024-08-18 16:19   ` Rob Herring (Arm)
2024-08-18 16:19 ` [PATCH 1/2] dt-bindings: clock: qcom,sc7280-lpasscorecc: order properties to match convention Rob Herring (Arm)
2024-12-17 16:38 ` Bjorn Andersson [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=173445353299.470882.2185588952896722099.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@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: 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

all inboxes | Powered by JetHome®