From: Jonathan Cameron <jic23@kernel.org>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "hslester96@gmail.com" <hslester96@gmail.com>,
"Popa, Stefan Serban" <StefanSerban.Popa@analog.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH] staging: iio: ad2s1210: Use device-managed API
Date: Sat, 27 Jul 2019 15:01:01 +0100 [thread overview]
Message-ID: <20190727150101.43bb4314@archlinux> (raw)
In-Reply-To: <b7c56658547a972b4e4a2b075b2319192f89c803.camel@analog.com>
On Fri, 26 Jul 2019 12:36:08 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> On Fri, 2019-07-26 at 19:07 +0800, Chuhong Yuan wrote:
> > [External]
> >
> > Use device-managed API to simplify the code.
> > The remove function is redundant now and can
> > be deleted.
>
> Reviewed-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
The end of this probe function is rather odd and probably needs sorting
out as I imagine that needs to happen before the device is exposed to
userspace.
Nothing to do with this patch though which is great.
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
>
> >
> > Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> > ---
> > drivers/staging/iio/resolver/ad2s1210.c | 12 +-----------
> > 1 file changed, 1 insertion(+), 11 deletions(-)
> >
> > diff --git a/drivers/staging/iio/resolver/ad2s1210.c b/drivers/staging/iio/resolver/ad2s1210.c
> > index 0c1bd108c386..4b25a3a314ed 100644
> > --- a/drivers/staging/iio/resolver/ad2s1210.c
> > +++ b/drivers/staging/iio/resolver/ad2s1210.c
> > @@ -671,7 +671,7 @@ static int ad2s1210_probe(struct spi_device *spi)
> > indio_dev->num_channels = ARRAY_SIZE(ad2s1210_channels);
> > indio_dev->name = spi_get_device_id(spi)->name;
> >
> > - ret = iio_device_register(indio_dev);
> > + ret = devm_iio_device_register(&spi->dev, indio_dev);
> > if (ret)
> > return ret;
> >
> > @@ -683,15 +683,6 @@ static int ad2s1210_probe(struct spi_device *spi)
> > return 0;
> > }
> >
> > -static int ad2s1210_remove(struct spi_device *spi)
> > -{
> > - struct iio_dev *indio_dev = spi_get_drvdata(spi);
> > -
> > - iio_device_unregister(indio_dev);
> > -
> > - return 0;
> > -}
> > -
> > static const struct of_device_id ad2s1210_of_match[] = {
> > { .compatible = "adi,ad2s1210", },
> > { }
> > @@ -710,7 +701,6 @@ static struct spi_driver ad2s1210_driver = {
> > .of_match_table = of_match_ptr(ad2s1210_of_match),
> > },
> > .probe = ad2s1210_probe,
> > - .remove = ad2s1210_remove,
> > .id_table = ad2s1210_id,
> > };
> > module_spi_driver(ad2s1210_driver);
prev parent reply other threads:[~2019-07-27 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 11:07 [PATCH] staging: iio: ad2s1210: Use device-managed API Chuhong Yuan
2019-07-26 12:36 ` Ardelean, Alexandru
2019-07-27 14:01 ` Jonathan Cameron [this message]
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=20190727150101.43bb4314@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=StefanSerban.Popa@analog.com \
--cc=alexandru.Ardelean@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hslester96@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).