From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org,
driverdevel <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staging: iio: Fix sparse endian warning
Date: Sun, 22 May 2016 09:56:41 +0200 [thread overview]
Message-ID: <CAMuHMdWbavoKYVF_RXtJYoW1x2ms1j3VSC-bFoaQmqKU1V3R4A@mail.gmail.com> (raw)
Hi Ksenija, Greg,
On Wed, Mar 23, 2016 at 12:06 PM, Ksenija Stanojevic
<ksenija.stanojevic@gmail.com> wrote:
> Fix following sparse warning:
> warning: cast to restricted __be16
Please include line number information so we know which line sparse
complains about.
> Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
> ---
> drivers/staging/iio/adc/ad7606_spi.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/iio/adc/ad7606_spi.c b/drivers/staging/iio/a=
dc/ad7606_spi.c
> index d873a51..825da07 100644
> --- a/drivers/staging/iio/adc/ad7606_spi.c
> +++ b/drivers/staging/iio/adc/ad7606_spi.c
> @@ -21,7 +21,8 @@ static int ad7606_spi_read_block(struct device *dev,
> {
> struct spi_device *spi =3D to_spi_device(dev);
> int i, ret;
> - unsigned short *data =3D buf;
> + unsigned short *data;
> + __be16 *bdata =3D buf;
>
> ret =3D spi_read(spi, buf, count * 2);
> if (ret < 0) {
> @@ -30,7 +31,7 @@ static int ad7606_spi_read_block(struct device *dev,
> }
>
> for (i =3D 0; i < count; i++)
> - data[i] =3D be16_to_cpu(data[i]);
> + data[i] =3D be16_to_cpu(bdata[i]);
This patch is completely bogus:
drivers/staging/iio/adc/ad7606_spi.c: In function =E2=80=98ad7606_spi_read_=
block=E2=80=99:
drivers/staging/iio/adc/ad7606_spi.c:34: warning: =E2=80=98data=E2=80=99 is=
used uninitialized
in this function
Hence please revert commit 87787e5ef727ff15f7c552cc48823b469f2eb41b
Author: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Date: Wed Mar 23 12:06:34 2016 +0100
Staging: iio: Fix sparse endian warning
BTW, what version of sparse are you using?
My (Ubuntu) version of sparse didn't complain about the original, neither d=
oes
the one I've just cloned from the master repository
(v0.5.0-44-g40791b94c56b1a6d)?
Hence I have no idea if fixing this by keeping the assignment of buf to dat=
a
is warned about....
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k=
.org
In personal conversations with technical people, I call myself a hacker. Bu=
t
when I'm talking to journalists I just say "programmer" or something like t=
hat.
-- Linus Torvalds
next reply other threads:[~2016-05-22 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 7:56 Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-23 11:06 [PATCH] Staging: iio: Fix sparse endian warning Ksenija Stanojevic
2016-03-28 14:37 ` 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=CAMuHMdWbavoKYVF_RXtJYoW1x2ms1j3VSC-bFoaQmqKU1V3R4A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=ksenija.stanojevic@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).