Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Simon Graham <simon.graham@virtualcomputer.com>, linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, chaoming_li@realsil.com.cn
Subject: Re: [PATCH v3] rtlwifi: Modify rtl_pci_init to return 0 on success
Date: Thu, 09 Feb 2012 09:15:25 -0600	[thread overview]
Message-ID: <4F33E30D.8030407@lwfinger.net> (raw)
In-Reply-To: <1328799314-28867-1-git-send-email-simon.graham@virtualcomputer.com>

On 02/09/2012 08:55 AM, Simon Graham wrote:
> Fixes problem where caller would think routine succeeded when it failed
> leading to divide by zero panic.
>
> Signed-off-by: Simon Graham<simon.graham@virtualcomputer.com>
> ---

ACKed-by: Larry Finger <Larry.Finger@lwfinger.net>

Simon: Congratulations - your mailer mangling problem seems to be fixed.

John: This is V3.3 and stable material. This bug goes back to at least 2.6.39.

Larry

>   drivers/net/wireless/rtlwifi/pci.c |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/rtlwifi/pci.c b/drivers/net/wireless/rtlwifi/pci.c
> index fb84707..16ec0c1 100644
> --- a/drivers/net/wireless/rtlwifi/pci.c
> +++ b/drivers/net/wireless/rtlwifi/pci.c
> @@ -1495,7 +1495,7 @@ static int rtl_pci_init(struct ieee80211_hw *hw, struct pci_dev *pdev)
>   		return err;
>   	}
>
> -	return 1;
> +	return 0;
>   }
>
>   static int rtl_pci_start(struct ieee80211_hw *hw)
> @@ -1866,7 +1866,7 @@ int __devinit rtl_pci_probe(struct pci_dev *pdev,
>   	}
>
>   	/* Init PCI sw */
> -	err = !rtl_pci_init(hw, pdev);
> +	err = rtl_pci_init(hw, pdev);
>   	if (err) {
>   		RT_TRACE(rtlpriv, COMP_ERR, DBG_EMERG, "Failed to init PCI\n");
>   		goto fail3;


      reply	other threads:[~2012-02-09 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 14:55 [PATCH v3] rtlwifi: Modify rtl_pci_init to return 0 on success Simon Graham
2012-02-09 15:15 ` Larry Finger [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=4F33E30D.8030407@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chaoming_li@realsil.com.cn \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=simon.graham@virtualcomputer.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