From: Jonathan Cameron <jic23@kernel.org>
To: Roberta Dobrescu <roberta.dobrescu@gmail.com>, linux-iio@vger.kernel.org
Cc: octavian.purdila@intel.com, daniel.baluta@intel.com,
lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
pmeerw@pmeerw.net
Subject: Re: [PATCH 2/2] iio: amplifiers: ad8366: Use right order for type specification
Date: Thu, 01 Jan 2015 12:17:10 +0000 [thread overview]
Message-ID: <54A53AC6.9050104@kernel.org> (raw)
In-Reply-To: <1419965144-3988-3-git-send-email-roberta.dobrescu@gmail.com>
On 30/12/14 18:45, Roberta Dobrescu wrote:
> This patch fixes the following checkpatch.pl warning:
> WARNING: type 'char unsigned' should be specified in [[un]signed]
> [short|int|long|long long] order
>
> Signed-off-by: Roberta Dobrescu <roberta.dobrescu@gmail.com>
Applied.
> ---
> drivers/iio/amplifiers/ad8366.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/amplifiers/ad8366.c b/drivers/iio/amplifiers/ad8366.c
> index fce25a0..c0d364e 100644
> --- a/drivers/iio/amplifiers/ad8366.c
> +++ b/drivers/iio/amplifiers/ad8366.c
> @@ -31,7 +31,7 @@ struct ad8366_state {
> };
>
> static int ad8366_write(struct iio_dev *indio_dev,
> - unsigned char ch_a, char unsigned ch_b)
> + unsigned char ch_a, unsigned char ch_b)
> {
> struct ad8366_state *st = iio_priv(indio_dev);
> int ret;
>
prev parent reply other threads:[~2015-01-01 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 18:45 [PATCH 0/2] iio: amplifiers: Fix checkpatch.pl warnings Roberta Dobrescu
2014-12-30 18:45 ` [PATCH 1/2] iio: amplifiers: ad8366: Remove space before ',' Roberta Dobrescu
2015-01-01 12:16 ` Jonathan Cameron
2014-12-30 18:45 ` [PATCH 2/2] iio: amplifiers: ad8366: Use right order for type specification Roberta Dobrescu
2015-01-01 12:17 ` 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=54A53AC6.9050104@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=daniel.baluta@intel.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=pmeerw@pmeerw.net \
--cc=roberta.dobrescu@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).