From: Marijn Suijten <marijn.suijten@somainline.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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 16:21:21 +0100 [thread overview]
Message-ID: <20230118152121.blb74eplrqz5rww2@SoMainline.org> (raw)
In-Reply-To: <Y8gCRECOja+FxRsf@smile.fi.intel.com>
On 2023-01-18 16:29:24, Andy Shevchenko wrote:
...
> The devm_kstrdup(fwnode_get_name()) is an open coded variant of the above.
> I don't think we need to open code and produce NIH even a single API. And
> no, there is no magic behind that. At least from the fwnode point of view.
>
> You may very well say that > 1500 instances of "%pOF" is a magic...
Forgive me for not having a clear definition of "open coding" in mind
(showing a different way of implementing something, compared to the
"status quo" that I was not yet aware of?), nor knowing what NIH is
supposed to mean in this context. We're in bike-shedding territory
anyway, guess I should just bookmark the page that details all the many
`%` format strings available.
...
> > I find the latter clearer as it doesn't require the reader to figure out
> > that name - name cancels itself out. Alternatively we can write
> > strchrnul(name, '@')[0].
>
> I don't like to have Pythonisms in the C code, really.
>
> P.S. I guess this little patch already emptied my bandwidth, so I leave
> any further discussion to you and IIO maintainers. Thank you for the
> review!
Just soaking up kernel coding standards here :)
- Marijn
next prev parent reply other threads:[~2023-01-18 15:24 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
2023-01-18 14:04 ` Marijn Suijten
2023-01-18 14:29 ` Andy Shevchenko
2023-01-18 15:21 ` Marijn Suijten [this message]
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=20230118152121.blb74eplrqz5rww2@SoMainline.org \
--to=marijn.suijten@somainline.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--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=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