From: David Julian Veenstra <davidjulianveenstra@gmail.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: lars@metafoo.de, jic23@kernel.org, Michael.Hennerich@analog.com,
knaack.h@gmx.de, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH 05/11] staging: iio: ad2s1200: Introduce variable for repeated value
Date: Sat, 24 Mar 2018 13:22:22 +0100 [thread overview]
Message-ID: <87efk9mznl.fsf@gmail.com> (raw)
In-Reply-To: <20180323141703.000028b5@huawei.com>
On 23, March 2018 14:17, Jonathan Cameron wrote:
> On Sun, 18 Mar 2018 14:35:46 +0100
> David Veenstra <davidjulianveenstra@gmail.com> wrote:
>
>> Add variable to hold &spi->dev in ad2s1200_probe. This value is repeatedly
>> used in ad2s1200_probe.
>>
>> Signed-off-by: David Veenstra <davidjulianveenstra@gmail.com>
> I'm a little unconvinced by this one. It adds code to save
> a really very trivial bit of repetition. If it had been
> via another pointer or this would have made a big difference
> in number of lines by bringing a lot of entries below 80 chars
> that weren't previous, then there would be a good argument.
>
> Here, not so much.
The 9th patch adds another 4 occurrences. So in total &st->dev appears
9 times in ad2s1200_probe. To me it seemed worth it to
introduce a variable for it. But I agree that it doesn't add much.
Best regards,
David Veenstra
>
> Jonathan
>> ---
>> drivers/staging/iio/resolver/ad2s1200.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/staging/iio/resolver/ad2s1200.c b/drivers/staging/iio/resolver/ad2s1200.c
>> index 00efba598671..eceb86e952de 100644
>> --- a/drivers/staging/iio/resolver/ad2s1200.c
>> +++ b/drivers/staging/iio/resolver/ad2s1200.c
>> @@ -118,19 +118,22 @@ static int ad2s1200_probe(struct spi_device *spi)
>> unsigned short *pins = spi->dev.platform_data;
>> struct ad2s1200_state *st;
>> struct iio_dev *indio_dev;
>> + struct device *dev;
>> int pn, ret = 0;
>>
>> + dev = &spi->dev;
>> +
>> for (pn = 0; pn < AD2S1200_PN; pn++) {
>> - ret = devm_gpio_request_one(&spi->dev, pins[pn], GPIOF_DIR_OUT,
>> + ret = devm_gpio_request_one(dev, pins[pn], GPIOF_DIR_OUT,
>> DRV_NAME);
>> if (ret) {
>> - dev_err(&spi->dev, "request gpio pin %d failed\n",
>> + dev_err(dev, "request gpio pin %d failed\n",
>> pins[pn]);
>> return ret;
>> }
>> }
>>
>> - indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*st));
>> + indio_dev = devm_iio_device_alloc(dev, sizeof(*st));
>> if (!indio_dev)
>> return -ENOMEM;
>>
>> @@ -141,14 +144,14 @@ static int ad2s1200_probe(struct spi_device *spi)
>> st->sample = pins[0];
>> st->rdvel = pins[1];
>>
>> - indio_dev->dev.parent = &spi->dev;
>> + indio_dev->dev.parent = dev;
>> indio_dev->info = &ad2s1200_info;
>> indio_dev->modes = INDIO_DIRECT_MODE;
>> indio_dev->channels = ad2s1200_channels;
>> indio_dev->num_channels = ARRAY_SIZE(ad2s1200_channels);
>> indio_dev->name = spi_get_device_id(spi)->name;
>>
>> - ret = devm_iio_device_register(&spi->dev, indio_dev);
>> + ret = devm_iio_device_register(dev, indio_dev);
>> if (ret)
>> return ret;
>>
next prev parent reply other threads:[~2018-03-24 12:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 13:33 [PATCH 00/11] staging: iio: ad2s1200: Driver clean up David Veenstra
2018-03-18 13:34 ` [PATCH 01/11] staging: iio: ad2s1200: Sort includes alphabetically David Veenstra
2018-03-18 13:34 ` [PATCH 02/11] staging: iio: ad2s1200: Reverse Christmas tree order David Veenstra
2018-03-18 13:34 ` [PATCH 03/11] staging: iio: ad2s1200: Add blank lines David Veenstra
2018-03-18 13:35 ` [PATCH 04/11] staging: iio: ad2s1200: Add kernel docs to driver state David Veenstra
2018-03-18 13:35 ` [PATCH 05/11] staging: iio: ad2s1200: Introduce variable for repeated value David Veenstra
2018-03-23 13:17 ` Jonathan Cameron
2018-03-24 12:22 ` David Julian Veenstra [this message]
2018-03-24 14:04 ` Jonathan Cameron
2018-03-18 13:35 ` [PATCH 06/11] staging: iio: ad2s1200: Improve readability with be16_to_cpup David Veenstra
2018-03-18 13:36 ` [PATCH 07/11] staging: iio: ad2s1200: Ensure udelay(1) in all necessary code paths David Veenstra
2018-03-23 13:20 ` Jonathan Cameron
2018-03-24 12:26 ` David Julian Veenstra
2018-03-18 13:36 ` [PATCH 08/11] staging: iio: ad2s1200: Replace legacy gpio ABI with modern ABI David Veenstra
2018-03-23 13:23 ` Jonathan Cameron
2018-03-18 13:36 ` [PATCH 09/11] staging: iio: ad2s1200: Add scaling factor for IIO_ANGL_VEL channel David Veenstra
2018-03-18 13:37 ` [PATCH 10/11] staging: iio: ad2s1200: Replace angle channel with inclination channel David Veenstra
2018-03-23 13:27 ` Jonathan Cameron
2018-03-24 12:36 ` David Julian Veenstra
2018-03-24 14:12 ` Jonathan Cameron
2018-03-24 14:57 ` David Julian Veenstra
2018-03-24 17:40 ` Jonathan Cameron
2018-03-18 13:37 ` [PATCH 11/11] Move resolver ad2c1200 driver out of staging to mainline iio David Veenstra
2018-03-23 13:29 ` 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=87efk9mznl.fsf@gmail.com \
--to=davidjulianveenstra@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.