From: Andrew Morton <akpm@linux-foundation.org>
To: Doug Thompson <norsk5@yahoo.com>
Cc: qingtao.cao@windriver.com, linux-kernel@vger.kernel.org,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: [v1 PATCH 3/8] EDAC: AMD8111 driver source file
Date: Wed, 11 Mar 2009 12:08:13 -0700 [thread overview]
Message-ID: <20090311120813.456762f1.akpm@linux-foundation.org> (raw)
In-Reply-To: <918342.94228.qm@web50101.mail.re2.yahoo.com>
On Wed, 11 Mar 2009 11:55:36 -0700 (PDT)
Doug Thompson <norsk5@yahoo.com> wrote:
>
> --- On Tue, 3/10/09, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > From: Andrew Morton <akpm@linux-foundation.org>
> > Subject: Re: [v1 PATCH 3/8] EDAC: AMD8111 driver source file
> > To: "Harry Ciao" <qingtao.cao@windriver.com>
> > Cc: linux-kernel@vger.kernel.org, bluesmoke-devel@lists.sourceforge.net
> > Date: Tuesday, March 10, 2009, 2:46 PM
> > On Mon,__ 9 Mar 2009 16:08:12
> > +0800
> > Harry Ciao <qingtao.cao@windriver.com>
> > wrote:
>
> <snip>
>
> > > +static void edac_pci_write_dword(struct pci_dev *dev,
> > int reg, u32 val32)
> > > +{
> > > +______ int ret;
> > > +
> > > +______ ret = pci_write_config_dword(dev,
> > reg, val32);
> > > +______ if (ret > 0)
> > > +______ ______ printk(KERN_ERR
> > AMD8111_EDAC_MOD_STR
> > > +______ ______
> > ______ " PCI Access Write Error at 0x%x\n",
> > reg);
> > > +}
> > > +
> > > +static void edac_pci_write_byte(struct pci_dev *dev,
> > int reg, u8 val8)
> > > +{
> > > +______ int ret;
> > > +
> > > +______ ret = pci_write_config_byte(dev,
> > reg, val8);
> > > +______ if (ret > 0)
> > > +______ ______ printk(KERN_ERR
> > AMD8111_EDAC_MOD_STR
> > > +______ ______
> > ______ " PCI Access Write Error at 0x%x\n",
> > reg);
> > > +}
> >
> >
> > <spends a while trying to work out what the return value
> > of
> > pci_read_config_dword() means>
> >
> > <gets frustrated and gives up>
> >
> > Is it correct that all of these functions treat a +ve
> > return value as
> > an error?
>
> Yes, the config APIs do return an error code on an operation error.
OK, but presumably they're negative error codes, so
if (ret > 0)
error()
isn't right.
<checks>
Harry has turned that into
if (ret != 0)
error();
which looks better.
next prev parent reply other threads:[~2009-03-11 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 18:55 [v1 PATCH 3/8] EDAC: AMD8111 driver source file Doug Thompson
2009-03-11 19:08 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-09 8:08 [v1 PATCH 0/8] Add AMD8111 and AMD8131 EDAC drivers Harry Ciao
2009-03-09 8:08 ` [v1 PATCH 1/8] EDAC: AMD8111 driver Kconfig & Makefile Harry Ciao
2009-03-09 8:08 ` [v1 PATCH 2/8] EDAC: AMD8111 driver header file Harry Ciao
2009-03-09 8:08 ` [v1 PATCH 3/8] EDAC: AMD8111 driver source file Harry Ciao
2009-03-10 20:46 ` Andrew Morton
2009-03-11 2:15 ` Harry Ciao
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=20090311120813.456762f1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.com \
--cc=qingtao.cao@windriver.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