From: Larry Finger <Larry.Finger@lwfinger.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linville@tuxdriver.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] bcm43xx_sprom_write(): add error checks
Date: Mon, 06 Nov 2006 09:50:03 -0600 [thread overview]
Message-ID: <454F59AB.9090403@lwfinger.net> (raw)
In-Reply-To: <20061106142146.GN5778@stusta.de>
Adrian Bunk wrote:
> The Coverity checker noted that these "if (err)"'s couldn't ever be
> true.
>
> It seems the intention was to check the return values of the
> bcm43xx_pci_write_config32()'s?
Exactly. This patch sent to wireless-2.6.
Thanks,
Larry
prev parent reply other threads:[~2006-11-06 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 14:21 [RFC: 2.6 patch] bcm43xx_sprom_write(): add error checks Adrian Bunk
2006-11-06 15:50 ` 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=454F59AB.9090403@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).