From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>, jacopo <jacopo@jmondi.org>
Cc: Arushi Singhal <arushisinghal19971997@gmail.com>,
outreachy-kernel@googlegroups.com,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: replace comma with a semicolon
Date: Sat, 1 Apr 2017 11:00:58 +0100 [thread overview]
Message-ID: <dd41628a-bd56-0ccf-0baf-238a717049aa@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1703301534380.24907@vps.pmeerw.net>
On 30/03/17 14:38, Peter Meerwald-Stadler wrote:
>
>> On Thu, Mar 30, 2017 at 06:16:03PM +0530, Arushi Singhal wrote:
>>> Replace a comma between expression statements by a semicolon. This
>>> changes the semantics of the code, but given the current indentation
>>> appears to be what is intended.
>
>> You can simply say that this fixes what appears to be a bug to me.
>> I wonder how this does even compile..
>
> it's valid C and I think it does the correct thing (i.e. assign those
> variables); the style is weird obviously
Hohum I am clearly going crazy in my old age.
Not a bug, but nice to fix so
Applied to the togreg branch of iio.git. Sorry for messing my little
change up Jacopo! Always worth checking a maintainer isn't being
an idiot when they apply your patches. As others will certify we
make plenty of mistakes.
Jonathan
>
>> [1] https://marc.info/?l=linux-iio&m=148475728729617&w=2
>>
>>> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
>>> ---
>>> drivers/iio/adc/max11100.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/iio/adc/max11100.c b/drivers/iio/adc/max11100.c
>>> index 23c060e1b663..1180bcc22ff1 100644
>>> --- a/drivers/iio/adc/max11100.c
>>> +++ b/drivers/iio/adc/max11100.c
>>> @@ -124,8 +124,8 @@ static int max11100_probe(struct spi_device *spi)
>>> indio_dev->name = "max11100";
>>> indio_dev->info = &max11100_info;
>>> indio_dev->modes = INDIO_DIRECT_MODE;
>>> - indio_dev->channels = max11100_channels,
>>> - indio_dev->num_channels = ARRAY_SIZE(max11100_channels),
>>> + indio_dev->channels = max11100_channels;
>>> + indio_dev->num_channels = ARRAY_SIZE(max11100_channels);
>>>
>>> state->vref_reg = devm_regulator_get(&spi->dev, "vref");
>>> if (IS_ERR(state->vref_reg))
>>> --
>>> 2.11.0
>>>
>>
>
next prev parent reply other threads:[~2017-04-01 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:46 Arushi Singhal
2017-03-30 13:30 ` jacopo
2017-03-30 13:38 ` Peter Meerwald-Stadler
2017-04-01 10:00 ` Jonathan Cameron [this message]
2017-03-30 17:23 ` Alexandre Belloni
2017-03-30 18:06 ` jacopo
2017-03-30 18:22 ` [Outreachy kernel] " Alison Schofield
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=dd41628a-bd56-0ccf-0baf-238a717049aa@kernel.org \
--to=jic23@kernel.org \
--cc=arushisinghal19971997@gmail.com \
--cc=jacopo@jmondi.org \
--cc=lars@metafoo.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®