From: Jonathan Cameron <jic23@kernel.org>
To: Marek Vasut <marex@denx.de>,
Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
devel@driverdev.osuosl.org, Brian Vandre <bvandre@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
devicetree@vger.kernel.org,
Vaishali Thakkar <vthakkar1994@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Peter Meerwald <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>,
Grant Likely <grant.likely@linaro.org>,
Robert Hodaszi <robert.hodaszi@digi.com>,
Darshana Padmadas <darshanapadmadas@gmail.com>
Subject: Re: [PATCH] staging: iio: adc: mxs-lradc: Change type in printf format string
Date: Sun, 08 Feb 2015 12:07:48 +0000 [thread overview]
Message-ID: <54D75194.40201@kernel.org> (raw)
In-Reply-To: <201501272359.59011.marex@denx.de>
On 27/01/15 22:59, Marek Vasut wrote:
> On Tuesday, January 27, 2015 at 11:23:33 PM, Rickard Strandqvist wrote:
>> Wrong type in printf format string, requires 'int'
>> but the argument type is 'unsigned int'
>>
>> This was found using a static code analysis program called cppcheck
>>
>> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
>
> Makes sense, thanks!
>
> Reviewed-by: Marek Vasut <marex@denx.de>
Applied.
>
> Best regards,
> Marek Vasut
>
prev parent reply other threads:[~2015-02-08 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 22:23 [PATCH] staging: iio: adc: mxs-lradc: Change type in printf format string Rickard Strandqvist
[not found] ` <1422397413-9447-1-git-send-email-rickard_strandqvist-IW2WV5XWFqGZkjO+N0TKoMugMpMbD5Xr@public.gmane.org>
2015-01-27 22:59 ` Marek Vasut
2015-02-08 12:07 ` Jonathan Cameron [this message]
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=54D75194.40201@kernel.org \
--to=jic23@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=bvandre@gmail.com \
--cc=darshanapadmadas@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=grant.likely@linaro.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=marex@denx.de \
--cc=pmeerw@pmeerw.net \
--cc=rickard_strandqvist@spectrumdigital.se \
--cc=robert.hodaszi@digi.com \
--cc=robh+dt@kernel.org \
--cc=vthakkar1994@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;
as well as URLs for NNTP newsgroup(s).