Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	~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>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/5] iio: adc: qcom-spmi-vadc: Propagate fw node label to userspace
Date: Mon, 1 May 2023 17:21:51 +0100	[thread overview]
Message-ID: <20230501172151.4a4b6dce@jic23-huawei> (raw)
In-Reply-To: <20230122234137.fyziba55n3b6tx3j@SoMainline.org>

On Mon, 23 Jan 2023 00:41:37 +0100
Marijn Suijten <marijn.suijten@somainline.org> wrote:

> On 2023-01-22 16:59:47, Jonathan Cameron wrote:
> > On Mon, 16 Jan 2023 23:09:04 +0100
> > Marijn Suijten <marijn.suijten@somainline.org> wrote:
> >   
> > > Implement read_label in qcom-spmi-vadc to see DT-specified label names
> > > in userspace.  At the same time clear up some documentation around
> > > extend_name to promote read_label, and normalize similar code in
> > > qcom-spmi-adc5.
> > >   
> > 
> > I think this is a good route forwards, but it is making changes
> > to ABI so I definitely want input on this from at least one of
> > the qualcomm maintainers before I pick it up - particularly
> > the changes in patch 3.
> > 
> > Don't want to cause anyone nasty surprises.  
> 
> Ack, patch 3 is the odd one of the bunch (as discussed many times
> prior).  It is an ABI break and would effectively obsolete "iio: adc:
> qcom-spmi-adc5: Fix the channel name" [1] as it then only affects a few
> dev_err/dev_dbg.  Let's wait and hear from Qcom maintainers.
> 
> [1]: https://lore.kernel.org/linux-arm-msm/20230118100623.42255-1-andriy.shevchenko@linux.intel.com/

Perhaps time for a resend of this series (drop the RFC marking as that
tends to mean people don't read things if they are low on time).

I'm going to mark this in patchwork as changes requested on basis a
v3 will show up shortly.

Thanks,

Jonathan

> 
> - Marijn


  reply	other threads:[~2023-05-01 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 22:09 [RFC PATCH v2 0/5] iio: adc: qcom-spmi-vadc: Propagate fw node label to userspace Marijn Suijten
2023-01-16 22:09 ` [RFC PATCH v2 1/5] iio: core: Point users of extend_name field to read_label callback Marijn Suijten
2023-01-18 16:19   ` Jonathan Cameron
2023-01-18 16:35     ` Marijn Suijten
2023-01-18 16:39       ` Marijn Suijten
2023-01-18 17:20       ` Jonathan Cameron
2023-01-16 22:09 ` [RFC PATCH v2 2/5] iio: adc: qcom-spmi-adc5: Use driver datasheet_name instead of DT label Marijn Suijten
2023-01-16 22:09 ` [RFC PATCH v2 3/5] iio: adc: qcom-spmi-adc5: Fall back to datasheet_name instead of fwnode name Marijn Suijten
2023-01-16 22:09 ` [RFC PATCH v2 4/5] iio: adc: qcom-spmi-adc5: Remove unnecessary datasheet_name NULL check Marijn Suijten
2023-01-16 22:09 ` [RFC PATCH v2 5/5] iio: adc: qcom-spmi-vadc: Propagate fw node label to userspace Marijn Suijten
2023-01-22 16:59 ` [RFC PATCH v2 0/5] " Jonathan Cameron
2023-01-22 23:41   ` Marijn Suijten
2023-05-01 16:21     ` Jonathan Cameron [this message]
2023-05-01 23:20       ` 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=20230501172151.4a4b6dce@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=jami.kettunen@somainline.org \
    --cc=konrad.dybcio@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=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=phone-devel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox