devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] arm64: dts: qcom: msm8916/39: Clean up MDSS labels
Date: Mon, 29 May 2023 17:31:05 +0200	[thread overview]
Message-ID: <ZHTFOZFxq-JgLP-p@gerhold.net> (raw)
In-Reply-To: <343e2e95-17ee-f5e3-61e9-7e0b793859a6@linaro.org>

On Mon, May 29, 2023 at 04:26:09PM +0100, Bryan O'Donoghue wrote:
> On 29/05/2023 16:24, Bryan O'Donoghue wrote:
> > On 29/05/2023 16:00, Stephan Gerhold wrote:
> > > Do you mean update the examples in the yaml bindings
> > 
> > Yep.
> > 
> > grep dsi0_out Documentation/* -r | grep qcom
> > grep dsi0_in Documentation/* -r | grep qcom
> > 
> > Consider splitting this patch out and fixing up[1] Documentation/* and
> > arch/arm/boot/dts/*.dts[i] , arch/arm64/boot/dts/qcom/*.dts[i]
> > 
> > We may as well be consistent everywhere.
> > 
> > ---
> > bod
> 
> 
> [1] In a standalone series
> 

Right I will check this and try to adjust the documentation and/or the
other SoCs in a separate series. I would still prefer to apply it for
8916/8939 as part of this series since I have some unrelated follow-up
changes that would just cause unnecessary conflicts for Bjorn otherwise.

We already have most newer SoCs using the naming convention in this
patch so it definitely does not make the existing situation any worse. :)

Thanks,
Stephan

  reply	other threads:[~2023-05-29 15:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 12:46 [PATCH 0/6] arm64: dts: qcom: msm8916/39: Clean up labels Stephan Gerhold
2023-05-29 12:46 ` [PATCH 1/6] arm64: dts: qcom: msm8916: Rename &msmgpio -> &tlmm Stephan Gerhold
2023-05-29 13:20   ` Bryan O'Donoghue
2023-05-29 12:46 ` [PATCH 2/6] arm64: dts: qcom: msm8916/39: Rename &blsp1_uartN -> &blsp_uartN Stephan Gerhold
2023-05-29 13:21   ` Bryan O'Donoghue
2023-05-29 12:47 ` [PATCH 3/6] arm64: dts: qcom: msm8916/39: Use consistent name for I2C/SPI pinctrl Stephan Gerhold
2023-05-29 13:26   ` Bryan O'Donoghue
2023-05-29 12:47 ` [PATCH 4/6] arm64: dts: qcom: msm8916/39: Clean up MDSS labels Stephan Gerhold
2023-05-29 13:33   ` Bryan O'Donoghue
2023-05-29 15:00     ` Stephan Gerhold
2023-05-29 15:24       ` Bryan O'Donoghue
2023-05-29 15:26         ` Bryan O'Donoghue
2023-05-29 15:31           ` Stephan Gerhold [this message]
2023-05-29 15:52             ` Konrad Dybcio
2023-05-29 12:47 ` [PATCH 5/6] arm64: dts: qcom: pm8916: Rename &wcd_codec -> &pm8916_codec Stephan Gerhold
2023-05-29 13:47   ` Bryan O'Donoghue
2023-05-29 15:07     ` Stephan Gerhold
2023-05-29 12:47 ` [PATCH 6/6] arm64: dts: qcom: msm8916: Move aliases to boards Stephan Gerhold
2023-05-29 13:48   ` Bryan O'Donoghue
2023-05-30  0:16 ` [PATCH 0/6] arm64: dts: qcom: msm8916/39: Clean up labels Bjorn Andersson

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=ZHTFOZFxq-JgLP-p@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).