netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: wg@grandegger.com, linux@dominikbrodowski.net,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 4/20 V2] drivers/net/can/sja1000/peak_pcmcia.c: fix error return code
Date: Fri, 05 Oct 2012 23:07:06 +0200	[thread overview]
Message-ID: <506F4BFA.2090006@pengutronix.de> (raw)
In-Reply-To: <1349469667-6137-4-git-send-email-peter.senna@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

On 10/05/2012 10:41 PM, Peter Senna Tschudin wrote:
> From: Peter Senna Tschudin <peter.senna@gmail.com>
> 
> The function pcan_probe() return 0 for success and negative value
> for most of its internal tests failures. There is one exception
> that is error case going to probe_err_4:. Fore this error case, the
> function abort its success execution path but returns non negative
> value, making it difficult for a caller function to notice the error.
> 
> This patch fixes the error case that do not return negative value.
> 
> This was found by Coccinelle, but the code change was made by hand.
> This patch is not robot generated.
> 
> A simplified version of the semantic match that finds this problem is
> as follows: (http://coccinelle.lip6.fr/)
> 
> // <smpl>
> (
> if@p1 (\(ret < 0\|ret != 0\))
>  { ... return ret; }
> |
> ret@p1 = 0
> )
> ... when != ret = e1
>     when != &ret
> *if(...)
> {
>   ... when != ret = e2
>       when forall
>  return ret;
> }
> // </smpl>
> 
> Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>


Too late, v1 of this patch is already in net/master

regards, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2012-10-05 21:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 20:41 [PATCH 1/20 V2] drivers/net/ethernet/dec/tulip/dmfe.c: fix error return code Peter Senna Tschudin
2012-10-05 20:41 ` [PATCH 2/20 V2] drivers/net/ethernet/natsemi/natsemi.c: " Peter Senna Tschudin
2012-10-05 21:40   ` Francois Romieu
2012-10-07 18:38   ` David Miller
2012-10-05 20:41 ` [PATCH 3/20 V2] drivers/net/can/sja1000/peak_pci.c: " Peter Senna Tschudin
2012-10-05 21:06   ` Marc Kleine-Budde
2012-10-07 18:38   ` David Miller
2012-10-05 20:41 ` [PATCH 4/20 V2] drivers/net/can/sja1000/peak_pcmcia.c: " Peter Senna Tschudin
2012-10-05 21:07   ` Marc Kleine-Budde [this message]
2012-10-07 18:38   ` David Miller
2012-10-05 20:41 ` [PATCH 5/20 V2] drivers/net/ethernet/sis/sis900.c: " Peter Senna Tschudin
2012-10-07 18:38   ` David Miller
2012-10-07 18:37 ` [PATCH 1/20 V2] drivers/net/ethernet/dec/tulip/dmfe.c: " David Miller

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=506F4BFA.2090006@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=netdev@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    --cc=wg@grandegger.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).