From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Kent Gustavsson <kent@minoris.se>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Cosmin Tanislav <demonsingur@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
ChiYuan Huang <cy_huang@richtek.com>,
Haibo Chen <haibo.chen@nxp.com>,
Ramona Bolboaca <ramona.bolboaca@analog.com>,
Ibrahim Tilki <Ibrahim.Tilki@analog.com>,
ChiaEn Wu <chiaen_wu@richtek.com>,
William Breathitt Gray <william.gray@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/4] iio: adc: mcp3911: simplify usage of spi->dev in probe function
Date: Tue, 8 Aug 2023 17:08:05 +0300 [thread overview]
Message-ID: <ZNJMReTpBOQ9FA2p@smile.fi.intel.com> (raw)
In-Reply-To: <20230808110432.240773-2-marcus.folkesson@gmail.com>
On Tue, Aug 08, 2023 at 01:04:30PM +0200, Marcus Folkesson wrote:
> Replace the usage of adc->spi->dev with spi->dev to make the code prettier.
Suggested-by: ?
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
...
> - adc->vref = devm_regulator_get_optional(&adc->spi->dev, "vref");
> + adc->vref = devm_regulator_get_optional(&spi->dev, "vref");
Why not
struct device *dev = &spi->dev;
and all the rest accordingly?
> if (IS_ERR(adc->vref)) {
> if (PTR_ERR(adc->vref) == -ENODEV) {
> adc->vref = NULL;
> } else {
> - dev_err(&adc->spi->dev,
> + dev_err(&spi->dev,
> "failed to get regulator (%ld)\n",
> PTR_ERR(adc->vref));
> return PTR_ERR(adc->vref);
Actually, you may first to switch to dev_err_probe() with the above introduced
struct device *dev = &spi->dev;
...
return dev_err_probe(dev, PTR_ERR(adc->vref),
"failed to get regulator\n",
and in the second patch do what you are doing here.
Will be much less changes and neater code at the end.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-08 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:04 [PATCH v4 1/4] dt-bindings: iio: adc: mcp3911: add support for the whole MCP39xx family Marcus Folkesson
2023-08-08 11:04 ` [PATCH v4 2/4] iio: adc: mcp3911: simplify usage of spi->dev in probe function Marcus Folkesson
2023-08-08 14:08 ` Andy Shevchenko [this message]
2023-08-08 11:04 ` [PATCH v4 3/4] iio: adc: mcp3911: fix indentation Marcus Folkesson
2023-08-08 14:13 ` Andy Shevchenko
2023-08-08 11:04 ` [PATCH v4 4/4] iio: adc: mcp3911: add support for the whole MCP39xx family Marcus Folkesson
2023-08-08 14:23 ` Andy Shevchenko
2023-08-09 6:41 ` Marcus Folkesson
2023-08-09 18:02 ` Jonathan Cameron
2023-08-09 18:14 ` Krzysztof Kozlowski
2023-08-10 13:44 ` Andy Shevchenko
2023-08-10 14:31 ` Marcus Folkesson
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=ZNJMReTpBOQ9FA2p@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Ibrahim.Tilki@analog.com \
--cc=arnd@arndb.de \
--cc=chiaen_wu@richtek.com \
--cc=conor+dt@kernel.org \
--cc=cy_huang@richtek.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--cc=kent@minoris.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=ramona.bolboaca@analog.com \
--cc=robh+dt@kernel.org \
--cc=william.gray@linaro.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