mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Rob Herring <robh@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	Alexandru M Stan <amstan@chromium.org>,
	Julius Werner <jwerner@chromium.org>,
	"Joseph S . Barrera III" <joebar@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] dt-bindings: arm: qcom: Add more sc7180 Chromebook board bindings
Date: Tue, 17 May 2022 09:23:05 +0200	[thread overview]
Message-ID: <c948c2ed-d222-5c16-4df4-daf078c886cc@linaro.org> (raw)
In-Reply-To: <CAD=FV=XR+WwWmrB1wGX65=szBc2PbGNOHbm2tiQT5Wp8CPG0Kg@mail.gmail.com>

On 16/05/2022 17:16, Doug Anderson wrote:
> Hi,
> 
> On Mon, May 16, 2022 at 12:05 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 13/05/2022 18:59, Douglas Anderson wrote:
>>> This adds board bindings for boards that are downstream but not quite
>>> upstream yet.
>>>
>>> Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>> ---
>>>
>>> Changes in v2:
>>> - Use a "description" instead of a comment for each item.
>>> - Use the marketing name instead of the code name where possible.
>>
>> These should be published with the patch adding their upstream DTS/DTSI.
>> There is no point to list all possible boards in the world from any
>> downstream source. For upstream there is no particular benefit for such
>> bindings, for downstream you also said there is no.
> 
> Joe has been working on upstreaming these boards:
> 
> https://lore.kernel.org/r/20220510154406.v5.1.Id769ddc5dbf570ccb511db96da59f97d08f75a9c@changeid/
> 
> I think there is little chance that they won't go upstream at this
> point. However, we're at a time in the merge window where it will be
> several weeks before anything can land. If Joe were to include this
> patch as part of his series I suspect it would be much more confusing
> because it would add an unnecessary dependency between my series and
> his and make it harder for Bjorn to apply it later. Keeping the patch
> with my series means that the series can be applied more easily.
> 
> How about: I'll add a link to his latest posting in my next version.
> Then, in the future (after these bindings patches have landed) then
> future boards can go together with their bindings.


Sure, sounds good.


Best regards,
Krzysztof

  reply	other threads:[~2022-05-17  7:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 16:59 [PATCH v2 1/4] dt-bindings: Document how Chromebooks with depthcharge boot Douglas Anderson
2022-05-13 16:59 ` [PATCH v2 2/4] dt-bindings: arm: qcom: Add sc7180 Chromebook board bindings Douglas Anderson
2022-05-13 19:25   ` Matthias Kaehlcke
2022-05-16  7:01   ` Krzysztof Kozlowski
2022-05-16 15:01     ` Doug Anderson
2022-05-16 15:06       ` Krzysztof Kozlowski
2022-05-13 16:59 ` [PATCH v2 3/4] dt-bindings: arm: qcom: Add / fix sc7280 " Douglas Anderson
2022-05-13 19:36   ` Matthias Kaehlcke
2022-05-16  7:02   ` Krzysztof Kozlowski
2022-05-13 16:59 ` [PATCH v2 4/4] dt-bindings: arm: qcom: Add more sc7180 Chromebook " Douglas Anderson
2022-05-13 20:37   ` Matthias Kaehlcke
2022-05-13 20:44     ` Doug Anderson
2022-05-16  7:05   ` Krzysztof Kozlowski
2022-05-16 15:16     ` Doug Anderson
2022-05-17  7:23       ` Krzysztof Kozlowski [this message]
2022-05-13 18:42 ` [PATCH v2 1/4] dt-bindings: Document how Chromebooks with depthcharge boot Matthias Kaehlcke
2022-05-16  6:57 ` Krzysztof Kozlowski
2022-05-16 15:06   ` Doug Anderson
2022-05-16 15:11     ` Krzysztof Kozlowski

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=c948c2ed-d222-5c16-4df4-daf078c886cc@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=amstan@chromium.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=joebar@chromium.org \
    --cc=jwerner@chromium.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=quic_rjendra@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@codeaurora.org \
    --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

all inboxes | Powered by JetHome®