From: Ico Doornekamp <ico@pruts.nl>
To: Alison Schofield <amsfield22@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] io: adc: ad7606_core: fix signed/unsigned number comparison
Date: Sat, 01 Oct 2016 19:27:22 +0200 [thread overview]
Message-ID: <1475342724-sup-634@pruts.nl> (raw)
In-Reply-To: <20161001164932.GA2815@d830.WORKGROUP>
* On 2016-10-01 18:49:33 +0200, Alison Schofield wrote:
> Flattering the maintainer, always good and so true, so true :)
Knowing when to flatter whom is often more imporant then cranking out
sweet code :)
> Here's something found by sparse for little penguin.
> See the Outreachy tasks page. https://kernelnewbies.org/IIO_tasks
>
> You'll see I leveraged your IIO_CHAN* patch for the first coding task.
> We have a second coding task for sparse endianness patches. There are
> some remaining. If you tell me you're grabbing one, I'll put it on
> our claimed page so an applicant doesn't start on it.
>
> I know this one is unclaimed at the moment:
> CHECK drivers/iio/magnetometer/ak8974.c
> drivers/iio/magnetometer/ak8974.c:403:16: warning: cast to restricted
> __le16
> drivers/iio/magnetometer/ak8974.c:480:24: warning: cast to restricted
> __le16
Ah, great, I missed those. Patch following. Thanks,
--
:wq
^X^Cy^K^X^C^C^C^C
prev parent reply other threads:[~2016-10-01 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 13:41 [PATCH] io: adc: ad7606_core: fix signed/unsigned number comparison Ico Doornekamp
2016-10-01 16:09 ` Jonathan Cameron
2016-10-01 16:17 ` Ico Doornekamp
2016-10-01 16:49 ` Alison Schofield
2016-10-01 17:27 ` Ico Doornekamp [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=1475342724-sup-634@pruts.nl \
--to=ico@pruts.nl \
--cc=amsfield22@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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).