All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marijn Suijten <marijn.suijten@somainline.org>,
	phone-devel@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
	AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@somainline.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Martin Botka <martin.botka@somainline.org>,
	Jami Kettunen <jami.kettunen@somainline.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 5/5] dt-bindings: iio: adc: Require generic `channel` name for channel nodes
Date: Tue, 11 Apr 2023 08:09:09 +0200	[thread overview]
Message-ID: <df0ec7ac-f472-c307-6f84-950f17d5ddba@linaro.org> (raw)
In-Reply-To: <20230410202917.247666-6-marijn.suijten@somainline.org>

On 10/04/2023 22:29, Marijn Suijten wrote:
> As discussed in [1] it is more convenient to use a generic `channel`
> node name for ADC channels while storing a friendly - board-specific
> instead of PMIC-specific - name in the label, if/when desired to
> overwrite the channel description already contained (but previously
> unused) in the driver [2].
> 


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2023-04-11  6:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 20:29 [PATCH v4 0/5] dts: qcom: Use labels with generic node names for ADC channels Marijn Suijten
2023-04-10 20:29 ` [PATCH v4 1/5] ARM: " Marijn Suijten
2023-04-10 20:29 ` [PATCH v4 2/5] arm64: " Marijn Suijten
2023-04-10 20:29 ` [PATCH v4 3/5] dt-bindings: thermal: Use generic ADC node name in examples Marijn Suijten
2023-04-11  6:08   ` Krzysztof Kozlowski
2023-04-17  7:41   ` Daniel Lezcano
2023-04-10 20:29 ` [PATCH v4 4/5] dt-bindings: mfd: qcom,spmi-pmic: " Marijn Suijten
2023-04-11  6:08   ` Krzysztof Kozlowski
2023-04-20 10:21   ` Lee Jones
2023-04-10 20:29 ` [PATCH v4 5/5] dt-bindings: iio: adc: Require generic `channel` name for channel nodes Marijn Suijten
2023-04-11  6:09   ` Krzysztof Kozlowski [this message]
2023-04-12 20:27   ` Jonathan Cameron
2023-04-12 20:31     ` Marijn Suijten
2023-04-15 16:49       ` Jonathan Cameron
2023-05-01 16:18         ` Jonathan Cameron
2023-05-01 21:56           ` Marijn Suijten

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=df0ec7ac-f472-c307-6f84-950f17d5ddba@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jami.kettunen@somainline.org \
    --cc=jic23@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.