linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
	linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: [PATCH1/2] Fix return value handling
Date: Mon, 23 Mar 2009 12:11:09 -0400	[thread overview]
Message-ID: <1237824669.14758.16.camel@localhost.localdomain> (raw)
In-Reply-To: <200903231659.48903.marek.vasut@gmail.com>

On Mon, 2009-03-23 at 16:59 +0100, Marek Vasut wrote:
> On Monday 23 of March 2009 16:57:24 Marek Vasut wrote:
> > Hi,
> > here is a resend. One patch per mail.
> sorry, inlining
> 
> From fd2e610a87a8372cbc513e336fa71e3438742c9d Mon Sep 17 00:00:00 2001
> From: Marek Vasut <marek.vasut@gmail.com>
> Date: Mon, 23 Mar 2009 15:57:11 +0100
> Subject: [PATCH 1/2] Firmware loading functions can return possitive values
>  This is not a bug, but take it into consideration and handle it properly.

This patch should no longer be required, since the patch "libertas: fix
CF firmware loading for some cards" was applied.  The firmware helpers
should only return an error (< 0) or 0 (success).

Dan

> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> ---
>  drivers/net/wireless/libertas/if_cs.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/wireless/libertas/if_cs.c 
> b/drivers/net/wireless/libertas/if_cs.c
> index 842a08d..3f02e6a 100644
> --- a/drivers/net/wireless/libertas/if_cs.c
> +++ b/drivers/net/wireless/libertas/if_cs.c
> @@ -867,9 +867,9 @@ static int if_cs_probe(struct pcmcia_device *p_dev)
>  
>  	/* Load the firmware early, before calling into libertas.ko */
>  	ret = if_cs_prog_helper(card);
> -	if (ret == 0)
> +	if (ret >= 0)
>  		ret = if_cs_prog_real(card);
> -	if (ret)
> +	if (ret < 0)
>  		goto out2;
>  
>  	/* Make this card known to the libertas driver */


  reply	other threads:[~2009-03-23 16:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22  0:27 [PATCH] Marvell CF8381 Marek Vasut
2009-03-22  4:11 ` Marek Vasut
2009-03-22  8:04   ` Johannes Berg
2009-03-22 13:01     ` Marek Vasut
2009-03-22 13:03       ` Johannes Berg
2009-03-23 12:27   ` Holger Schurig
2009-03-23 16:15     ` Dan Williams
2009-03-23 21:58       ` Marek Vasut
2009-03-23 23:08         ` Dan Williams
2009-03-23 23:42           ` Marek Vasut
2009-03-24 10:26             ` Dan Williams
2009-03-24 20:01               ` John W. Linville
2009-03-24 20:33                 ` Marek Vasut
2009-03-23 12:13 ` Holger Schurig
2009-03-23 14:34   ` Marek Vasut
2009-03-23 15:57   ` [PATCH1/2] Fix return value handling Marek Vasut
2009-03-23 15:59     ` Marek Vasut
2009-03-23 16:11       ` Dan Williams [this message]
2009-03-23 15:59   ` [PATCH] Marvell CF8381 and CF8305 Marek Vasut
2009-03-23 16:00     ` Marek Vasut
2009-03-23 16:06       ` Holger Schurig
2009-03-23 17:09         ` Marek Vasut
2009-03-23 17:19           ` Dan Williams
2009-03-23 17:39             ` Marek Vasut
2009-03-23 16:58       ` Dan Williams

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=1237824669.14758.16.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marek.vasut@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).