public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
To: <ludovic.desroches@atmel.com>, <wsa@the-dreams.de>,
	<linux-i2c@vger.kernel.org>
Cc: <nicolas.ferre@atmel.com>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/1] i2c: at91: fix code checker warnings
Date: Thu, 11 Jun 2015 11:26:20 +0200	[thread overview]
Message-ID: <5579543C.6040108@atmel.com> (raw)
In-Reply-To: <cover.1434013494.git.cyrille.pitchen@atmel.com>

Hi all,

this patch was made after applying the previous series
"[PATCH v6 0/6] i2c: at91: add support to FIFOs and alternative command",
which was already accepted.

Best Regards,

Cyrille

Le 11/06/2015 11:16, Cyrille Pitchen a écrit :
> ChangeLog
> 
> v1:
> This patch fixes somes code checker warnings reported by Wolfram Sang:
> 
> drivers/i2c/busses/i2c-at91.c:213: style: Checking if unsigned variable 'buf_len' is less than zero.
> drivers/i2c/busses/i2c-at91.c:254: style: Checking if unsigned variable 'buf_len' is less than zero.
> drivers/i2c/busses/i2c-at91.c:293: style: Checking if unsigned variable 'buf_len' is less than zero.
> 
> Thanks for reporting!
> 
> Cyrille Pitchen (1):
>   i2c: at91: fix code checker warnings
> 
>  drivers/i2c/busses/i2c-at91.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 


      parent reply	other threads:[~2015-06-11  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  9:16 [PATCH 0/1] i2c: at91: fix code checker warnings Cyrille Pitchen
2015-06-11  9:16 ` [PATCH 1/1] " Cyrille Pitchen
2015-06-11 12:16   ` Ludovic Desroches
2015-06-11 13:18   ` Wolfram Sang
2015-06-11  9:26 ` Cyrille Pitchen [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=5579543C.6040108@atmel.com \
    --to=cyrille.pitchen@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=wsa@the-dreams.de \
    /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