From: Jonathan Cameron <jic23@cam.ac.uk>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: add mcp4725 I2C DAC driver
Date: Fri, 08 Jun 2012 08:34:19 +0100 [thread overview]
Message-ID: <4FD1AAFB.2050302@cam.ac.uk> (raw)
In-Reply-To: <alpine.DEB.2.01.1206080909380.26184@pmeerw.net>
On 6/8/2012 8:12 AM, Peter Meerwald wrote:
> Hello Jonathan,
>
>> from reading the code. Anyhow few things came up via sparse and and
>> my arm toolchain... (not sure which version off the top of my head)..
>
>> CHECK drivers/iio/dac/mcp4725.c
>> drivers/iio/dac/mcp4725.c:45:53: warning: incorrect type in argument 2
>> (different base types)
>> drivers/iio/dac/mcp4725.c:45:53: expected char const *buf
>> drivers/iio/dac/mcp4725.c:45:53: got unsigned char [usertype] (
>> *<noident> )[2]
>> drivers/iio/dac/mcp4725.c:58:53: warning: incorrect type in argument 2
>> (different base types)
>> drivers/iio/dac/mcp4725.c:58:53: expected char const *buf
>> drivers/iio/dac/mcp4725.c:58:53: got unsigned char [usertype] (
>> *<noident> )[2]
>> CC [M] drivers/iio/dac/mcp4725.o
>
> I did not know about sparse
>
> compiling out-of-tree with my toolchain did not yield above warnings,
> sorry for the extra review cycle
That's quite all right! I've done plenty of similar things myself
and had others poitn them out.
>
> regards, p.
>
next prev parent reply other threads:[~2012-06-08 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 8:30 [PATCH] iio: add mcp4725 I2C DAC driver Peter Meerwald
2012-06-07 16:07 ` Jonathan Cameron
2012-06-08 7:12 ` Peter Meerwald
2012-06-08 7:34 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-08 16:06 Peter Meerwald
2012-06-12 21:50 ` Greg KH
2012-06-08 7:07 Peter Meerwald
2012-06-08 7:36 ` Jonathan Cameron
2012-06-06 21:40 Peter Meerwald
2012-06-07 7:36 ` Jonathan Cameron
2012-04-30 10:27 [PATCH 2/2] " Jonathan Cameron
2012-04-30 13:54 ` [PATCH] " Peter Meerwald
2012-04-30 14:39 ` Jonathan Cameron
2012-04-30 18:37 ` Lars-Peter Clausen
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=4FD1AAFB.2050302@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=jic23@kernel.org \
--cc=linux-iio@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).