From: Jonathan Cameron <jic23@kernel.org>
To: Saalim Quadri <danascape@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: iio: adis16203: Remove unneeded spi_set_drvdata()
Date: Tue, 4 Mar 2025 14:32:30 +0000 [thread overview]
Message-ID: <20250304143230.6d91f64d@jic23-huawei> (raw)
In-Reply-To: <20250303180523.15445-1-danascape@gmail.com>
On Mon, 3 Mar 2025 23:35:23 +0530
Saalim Quadri <danascape@gmail.com> wrote:
> * Since we are making use of devm_iio_device_register(), we no longer
> need this nor do we have any spi_get_drvdata() in the driver.
>
Why have a single bullet point?
Also please rewrite in imperative sense. Something like
Driver no longer has a remove callback after conversion to fully
devm_ managed probe(). Remove now unneeded spi_get_drvdata()
as that value was previously on read in the remove() callback.
> Signed-off-by: Saalim Quadri <danascape@gmail.com>
Code is fine, so just this patch description stuff.
Thanks,
Jonathan
> ---
> drivers/staging/iio/accel/adis16203.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/staging/iio/accel/adis16203.c b/drivers/staging/iio/accel/adis16203.c
> index c1c73308800c..3faf3c61046a 100644
> --- a/drivers/staging/iio/accel/adis16203.c
> +++ b/drivers/staging/iio/accel/adis16203.c
> @@ -267,8 +267,6 @@ static int adis16203_probe(struct spi_device *spi)
> if (!indio_dev)
> return -ENOMEM;
> st = iio_priv(indio_dev);
> - /* this is only used for removal purposes */
> - spi_set_drvdata(spi, indio_dev);
>
> indio_dev->name = spi->dev.driver->name;
> indio_dev->channels = adis16203_channels;
next prev parent reply other threads:[~2025-03-04 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 18:05 [PATCH] staging: iio: adis16203: Remove unneeded spi_set_drvdata() Saalim Quadri
2025-03-04 14:32 ` Jonathan Cameron [this message]
2025-03-05 23:50 ` Saalim Quadri
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=20250304143230.6d91f64d@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=danascape@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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