public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	linux-arm-msm@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Andy Gross" <agross@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Konrad Dybcio" <konrad.dybcio@linaro.org>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>
Subject: Re: [PATCH v2 1/1] iio: adc: qcom-spmi-adc5: Fix the channel name
Date: Wed, 18 Jan 2023 15:22:42 +0200	[thread overview]
Message-ID: <Y8fyonSp49QoAb8v@smile.fi.intel.com> (raw)
In-Reply-To: <20230118123528.oaxtjbdier3ojd3m@SoMainline.org>

On Wed, Jan 18, 2023 at 01:35:28PM +0100, Marijn Suijten wrote:
> On 2023-01-18 12:06:23, Andy Shevchenko wrote:
> > The node name can contain an address part which is unused
> > by the driver. Moreover, this string is propagated into
> > the userspace label, sysfs filenames *and breaking ABI*.
> > 
> > Cut the address part out before assigning the channel name.
> > 
> > Fixes: 4f47a236a23d ("iio: adc: qcom-spmi-adc5: convert to device properties")
> > Reported-by: Marijn Suijten <marijn.suijten@somainline.org>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Reviewed-by: Marijn Suijten <marijn.suijten@somainline.org>

Thank you!

My answers below.

...

> > +	name = devm_kasprintf(dev, GFP_KERNEL, "%pfwP", fwnode);
> 
> Is this better/cleaner than copying the string from fwnode_get_name?

Coying to where? And what would be the lifetime of that string?

With devm_kasprintf():
- we don't care how long the string is
- we don't care about corner cases of lifetime as it's the same as
  device itself (i.o.w. the same as the IIO device container)

...

> > +	name[strchrnul(name, '@') - name] = '\0';
> 
> This is the same as *strchrnul(name, '@') = '\0'; if I'm not mistaken.

Yes, But it's harder to read and understand. I believe the compiler has
enough power to optimize this to the same assembly code.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-01-18 13:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 10:06 [PATCH v2 1/1] iio: adc: qcom-spmi-adc5: Fix the channel name Andy Shevchenko
2023-01-18 12:35 ` Marijn Suijten
2023-01-18 13:22   ` Andy Shevchenko [this message]
2023-01-18 14:04     ` Marijn Suijten
2023-01-18 14:29       ` Andy Shevchenko
2023-01-18 15:21         ` Marijn Suijten
2023-01-18 15:57           ` Andy Shevchenko
2023-01-22 17:24 ` Jonathan Cameron
2023-01-23 12:02   ` Andy Shevchenko
2023-01-23 19:30     ` Jonathan Cameron
2023-01-23 16:35   ` Konrad Dybcio
2023-01-23 17:01     ` Marijn Suijten
2023-01-23 17:04       ` Konrad Dybcio
2023-01-23 23:12     ` Doug Anderson
2023-01-25 19:39       ` Matthias Kaehlcke
2023-01-28 15:34         ` Jonathan Cameron

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=Y8fyonSp49QoAb8v@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=jic23@kernel.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=nuno.sa@analog.com \
    /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