From: Jonathan Cameron <jic23@kernel.org>
To: simran singhal <singhalsimran0@gmail.com>, lars@metafoo.de
Cc: Michael.Hennerich@analog.com, knaack.h@gmx.de,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v1 09/10] staging: iio: resolver: Remove exceptional & on function name
Date: Sat, 11 Mar 2017 18:45:02 +0000 [thread overview]
Message-ID: <f20cc799-fba7-84b2-b271-9620c370ace7@kernel.org> (raw)
In-Reply-To: <1489242404-12352-10-git-send-email-singhalsimran0@gmail.com>
On 11/03/17 14:26, simran singhal wrote:
> Remove & from function pointers to conform to the style found elsewhere
> in the file. Done using the following semantic patch
>
> // <smpl>
> @r@
> identifier f;
> @@
>
> f(...) { ... }
> @@
> identifier r.f;
> @@
>
> - &f
> + f
> // </smpl>
>
> Signed-off-by: simran singhal <singhalsimran0@gmail.com>
Given there aren't any other functional pointers in some the ad2s90
I have amended the patch title to reflect that we are changing
this to have consistency across drivers in the wider subsystem.
Far as I'm concerned, it's nice to tidy up. I'm not (currently)
advocating a tree wide sweep for these as the churn would be excessive
but it's not a bad thing to do in the staging drivers in my opinion!
Thanks,
Jonathan
> ---
> drivers/staging/iio/resolver/ad2s1200.c | 2 +-
> drivers/staging/iio/resolver/ad2s90.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/iio/resolver/ad2s1200.c b/drivers/staging/iio/resolver/ad2s1200.c
> index 82b2d88..a37e199 100644
> --- a/drivers/staging/iio/resolver/ad2s1200.c
> +++ b/drivers/staging/iio/resolver/ad2s1200.c
> @@ -97,7 +97,7 @@ static const struct iio_chan_spec ad2s1200_channels[] = {
> };
>
> static const struct iio_info ad2s1200_info = {
> - .read_raw = &ad2s1200_read_raw,
> + .read_raw = ad2s1200_read_raw,
> .driver_module = THIS_MODULE,
> };
>
> diff --git a/drivers/staging/iio/resolver/ad2s90.c b/drivers/staging/iio/resolver/ad2s90.c
> index 5b1c0db..b227090 100644
> --- a/drivers/staging/iio/resolver/ad2s90.c
> +++ b/drivers/staging/iio/resolver/ad2s90.c
> @@ -47,7 +47,7 @@ static int ad2s90_read_raw(struct iio_dev *indio_dev,
> }
>
> static const struct iio_info ad2s90_info = {
> - .read_raw = &ad2s90_read_raw,
> + .read_raw = ad2s90_read_raw,
> .driver_module = THIS_MODULE,
> };
>
>
next prev parent reply other threads:[~2017-03-11 18:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 14:26 [PATCH v1 00/10] staging: iio: Remove exceptional & on functions name simran singhal
2017-03-11 14:26 ` [PATCH v1 01/10] staging: iio: ad7192: Remove exceptional & on function name simran singhal
2017-03-11 18:36 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 02/10] staging: iio: ad7780: " simran singhal
2017-03-11 18:37 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 03/10] staging: iio: cdc: ad7746: " simran singhal
2017-03-11 18:39 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 04/10] staging: iio: cdc: ad7152: " simran singhal
2017-03-11 18:40 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 05/10] staging: iio: adis16240: " simran singhal
2017-03-11 18:40 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 06/10] staging: iio: adis16201: " simran singhal
2017-03-11 18:41 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 07/10] staging: iio: adis16209: " simran singhal
2017-03-11 18:41 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 08/10] staging: iio: adis16203: " simran singhal
2017-03-11 18:41 ` Jonathan Cameron
2017-03-11 14:26 ` [PATCH v1 09/10] staging: iio: resolver: " simran singhal
2017-03-11 18:45 ` Jonathan Cameron [this message]
2017-03-11 14:26 ` [PATCH v1 10/10] staging: iio: gyro: " simran singhal
2017-03-11 18:48 ` Jonathan Cameron
2017-03-11 18:57 ` Jonathan Cameron
2017-03-11 18:35 ` [PATCH v1 00/10] staging: iio: Remove exceptional & on functions name 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=f20cc799-fba7-84b2-b271-9620c370ace7@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=singhalsimran0@gmail.com \
/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®