From: Wolfram Sang <wsa@the-dreams.de>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: lee.jones@linaro.org, laurentiu.palcu@intel.com,
johan@kernel.org, julia.lawall@lip6.fr,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] i2c: dln2: simplify return flow for dln2_i2c_enable
Date: Thu, 13 Nov 2014 17:23:16 +0100 [thread overview]
Message-ID: <20141113162315.GC1275@katana> (raw)
In-Reply-To: <1415708457-18798-3-git-send-email-octavian.purdila@intel.com>
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
On Tue, Nov 11, 2014 at 02:20:57PM +0200, Octavian Purdila wrote:
> This fixes the following kbuild test robot warning:
>
> >> drivers/i2c/busses/i2c-dln2.c:70:1-4: WARNING: end returns can be simplified if negative or 0 value
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Reported-by: Julia Lawall <julia.lawall@lip6.fr>
>
> Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
Acked-by: Wolfram Sang <wsa@the-dreams.de>
Lee, I think it is easiest if you simply add it to the branch you have
for this driver. OK?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-13 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 12:20 [PATCH 0/2] fixes for ib-mfd-gpio-i2c-3.19 Octavian Purdila
2014-11-11 12:20 ` [PATCH 1/2] mfd: dln2: fix _dln2_transfer return code Octavian Purdila
2014-11-11 12:23 ` Johan Hovold
2014-11-11 16:18 ` Julia Lawall
2014-11-11 16:32 ` Octavian Purdila
2014-11-11 12:20 ` [PATCH 2/2] i2c: dln2: simplify return flow for dln2_i2c_enable Octavian Purdila
2014-11-11 12:26 ` Johan Hovold
2014-11-11 12:49 ` Octavian Purdila
2014-11-11 16:20 ` Julia Lawall
2014-11-12 10:39 ` Johan Hovold
2014-11-13 16:23 ` Wolfram Sang [this message]
2014-11-17 14:56 ` Lee Jones
2014-11-17 15:12 ` Octavian Purdila
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=20141113162315.GC1275@katana \
--to=wsa@the-dreams.de \
--cc=johan@kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=laurentiu.palcu@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.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