From: Francois Romieu <romieu@fr.zoreil.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Max Asbock <masbock@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ibmasm: add missing pci_enable_device()
Date: Tue, 10 Aug 2004 00:27:56 +0200 [thread overview]
Message-ID: <20040809222756.GA1555@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200408091128.35896.bjorn.helgaas@hp.com>
Bjorn Helgaas <bjorn.helgaas@hp.com> :
[...]
> > > ===== drivers/misc/ibmasm/module.c 1.2 vs edited =====
> > > --- 1.2/drivers/misc/ibmasm/module.c 2004-05-14 06:00:50 -06:00
> > > +++ edited/drivers/misc/ibmasm/module.c 2004-08-04 13:15:46 -06:00
> > > @@ -62,10 +62,17 @@
> > > int result = -ENOMEM;
> > > struct service_processor *sp;
> > >
> > > + if (pci_enable_device(pdev)) {
> > > + printk(KERN_ERR "%s: can't enable PCI device at %s\n",
> > > + DRIVER_NAME, pci_name(pdev));
> > > + return -ENODEV;
Btw, pci_enable_device returns a perfectly fine status code. There is no
reason to override it ('result = pci_enable_device(...' and you can even
remove the previous ENOMEM initialization).
[...]
> > > sp = kmalloc(sizeof(struct service_processor), GFP_KERNEL);
> > > if (sp == NULL) {
> > > dev_err(&pdev->dev, "Failed to allocate memory\n");
> > > - return result;
> > > + result = -ENOMEM;
> > > + goto error_kmalloc;
You may consider calling it err_pci_disable (or such). This way:
- one can check that the kmalloc is preceeded by a pci_enable;
- one can locally check that the unroll path does its job
(error_pci_disable is followed by a pci_disable_xxx -> makes sense).
--
Ueimor
next prev parent reply other threads:[~2004-08-09 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 21:32 Bjorn Helgaas
2004-08-09 17:18 ` Max Asbock
2004-08-09 17:28 ` Bjorn Helgaas
2004-08-09 22:27 ` Francois Romieu [this message]
[not found] <200408242224.i7OMOs1H029517@hera.kernel.org>
2004-08-25 0:43 ` Jeff Garzik
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=20040809222756.GA1555@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@us.ibm.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
all inboxes | Powered by JetHome®