devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Conor Dooley <conor@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Andy Gross <agross@kernel.org>,
	<cros-qcom-dts-watchers@chromium.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: ufs: qcom: Use 'ufshc' as the node name for UFS controller nodes
Date: Wed, 15 May 2024 09:07:44 +0100	[thread overview]
Message-ID: <20240515-untying-overbite-87bc0e55c673@wendy> (raw)
In-Reply-To: <20240515075005.GC2445@thinkpad>

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

On Wed, May 15, 2024 at 09:50:05AM +0200, Manivannan Sadhasivam wrote:
> On Tue, May 14, 2024 at 07:50:15PM +0100, Conor Dooley wrote:
> > On Tue, May 14, 2024 at 03:08:40PM +0200, Manivannan Sadhasivam wrote:
> > > Devicetree binding has documented the node name for UFS controllers as
> > > 'ufshc'. So let's use it instead of 'ufs' which is for the UFS devices.
> > 
> > Can you point out where that's been documented?
> 
> Typo here. s/Devicetree binding/Devicetree spec
> 
> https://github.com/devicetree-org/devicetree-specification/blob/main/source/chapter2-devicetree-basics.rst#generic-names-recommendation

Ah, that makes sense. I grepped for it in the kernel tree and didn't see
anything so I was a bit confused..

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2024-05-15  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 13:08 [PATCH 0/2] arm64: dts: qcom: Use 'ufshc' as the node name for UFS controller nodes Manivannan Sadhasivam
2024-05-14 13:08 ` [PATCH 1/2] dt-bindings: ufs: " Manivannan Sadhasivam
2024-05-14 18:50   ` Conor Dooley
2024-05-15  7:50     ` Manivannan Sadhasivam
2024-05-15  8:03       ` Krzysztof Kozlowski
2024-05-15  8:20         ` Manivannan Sadhasivam
2024-05-15  8:07       ` Conor Dooley [this message]
2024-05-15 19:17   ` Stephen Boyd
2024-05-14 13:08 ` [PATCH 2/2] arm64: dts: " Manivannan Sadhasivam
2024-05-15 19:17   ` Stephen Boyd
2024-10-24 14:59 ` (subset) [PATCH 0/2] " 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=20240515-untying-overbite-87bc0e55c673@wendy \
    --to=conor.dooley@microchip.com \
    --cc=agross@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=andersson@kernel.org \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@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).