From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
Cc: Himanshi Jain <himshijain.hj@gmail.com>,
outreachy-kernel@googlegroups.com, Michael.Hennerich@analog.com,
jic23@kernel.org, knaack.h@gmx.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: iio: adc: Added Space around binary op.
Date: Fri, 8 Sep 2017 11:37:56 +0200 [thread overview]
Message-ID: <2e3476f0-9e7e-2701-220a-5fb178d68d2e@metafoo.de> (raw)
In-Reply-To: <20170908103257.00002165@huawei.com>
On 09/08/2017 11:32 AM, Jonathan Cameron wrote:
> On Fri, 8 Sep 2017 07:29:06 +0100
> Jonathan Cameron <jic23@jic23.retrosnub.co.uk> wrote:
>
>> On 8 September 2017 05:47:52 BST, Himanshi Jain <himshijain.hj@gmail.com> wrote:
>>> Added space around(one on each side of) binary
>>> operator(-) as preferred according to kernel
>>> coding style.
>>>
>>> Signed-off-by: Himanshi Jain <himshijain.hj@gmail.com>
>>
>> Take a closer look at that macro. It isn't doing what you think...
>> To give a hint, changing this breaks userspace.
>
> Ok, I'm bored of this particular one coming up. When you have
> worked out what is going on Himanshi, would you mind putting
> together a patch adding a comment describing why it is a bad
> idea to 'fix' this? That would be a very useful patch as
> far as I'm concerned :)
>
> There aren't that many cases of this in IIO so adding a comment
> on each of them is probably reasonable just to avoid wasting
> people's time on fixing them! (I think we have had more than
> 5 such goes this year so far...)
>
I'd much rather fix this API so that you have to put "" around the name so
that it is clear that it is a string, rather than doing the implicit
conversion to string using preprocessor magic. Better to have a
self-documenting API then having to add a comment to each user of the API.
> Jonathan
>
>>
>> Jonathan
>>
>>
>>> ---
>>> drivers/staging/iio/adc/ad7192.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/staging/iio/adc/ad7192.c
>>> b/drivers/staging/iio/adc/ad7192.c
>>> index d11c6de..1aee662 100644
>>> --- a/drivers/staging/iio/adc/ad7192.c
>>> +++ b/drivers/staging/iio/adc/ad7192.c
>>> @@ -341,7 +341,7 @@ static int ad7192_setup(struct ad7192_state *st,
>>> }
>>>
>>> static IIO_DEVICE_ATTR_NAMED(in_v_m_v_scale_available,
>>> - in_voltage-voltage_scale_available,
>>> + in_voltage - voltage_scale_available,
>>> 0444, ad7192_show_scale_available, NULL, 0);
>>>
>>> static IIO_DEVICE_ATTR(in_voltage_scale_available, 0444,
>>
>
next prev parent reply other threads:[~2017-09-08 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 4:47 Himanshi Jain
2017-09-08 6:04 ` [Outreachy kernel] " Julia Lawall
2017-09-08 6:29 ` Jonathan Cameron
2017-09-08 9:32 ` Jonathan Cameron
2017-09-08 9:37 ` Lars-Peter Clausen [this message]
2017-09-08 9:46 ` Jonathan Cameron
2017-09-08 9:59 ` [Outreachy kernel] " Julia Lawall
2017-09-08 10:11 ` Lars-Peter Clausen
2017-09-08 10:32 ` Julia Lawall
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=2e3476f0-9e7e-2701-220a-5fb178d68d2e@metafoo.de \
--to=lars@metafoo.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=himshijain.hj@gmail.com \
--cc=jic23@jic23.retrosnub.co.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®