From: mikem@beardog.cca.cpqcorp.net
To: axboe@suse.de, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: cpqarray patches for 2.6 [5 of 5]
Date: Tue, 16 Mar 2004 10:49:22 -0600 [thread overview]
Message-ID: <20040316164922.GF21377@beardog.cca.cpqcorp.net> (raw)
This is patch 5 of 5. Please apply patches in order. All patches have been tested against 2.6.5-rc1.
Thanks,
mikem
-------------------------------------------------------------------------------
* Examines rc of pci_register_driver and returns
drivers/block/cpqarray.c | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
--- linux-2.6.1/drivers/block/cpqarray.c~cpqarray_pci_register_rc 2004-02-11 18:12:19.457511024 -0600
+++ linux-2.6.1-root/drivers/block/cpqarray.c 2004-02-11 18:22:06.566256928 -0600
@@ -318,9 +318,7 @@ MODULE_PARM(eisa, "1-8i");
*/
int __init cpqarray_init(void)
{
- if(cpqarray_init_step2() == 0) /* all the block dev num already used */
- return -ENODEV; /* or no controllers were found */
- return 0;
+ return (cpqarray_init_step2());
}
static void release_io_mem(ctlr_info_t *c)
@@ -559,18 +557,21 @@ static struct pci_driver cpqarray_pci_dr
};
/*
- * This is it. Find all the controllers and register them. I really hate
- * stealing all these major device numbers.
+ * This is it. Find all the controllers and register them.
* returns the number of block devices registered.
*/
int __init cpqarray_init_step2(void)
{
int num_cntlrs_reg = 0;
int i;
+ int rc = 0;
/* detect controllers */
printk(DRIVER_NAME "\n");
- pci_register_driver(&cpqarray_pci_driver);
+/* TODO: If it's an eisa only system, will rc return negative? */
+ rc = pci_register_driver(&cpqarray_pci_driver);
+ if (rc < 0)
+ return rc;
cpqarray_eisa_detect();
for (i=0; i < MAX_CTLR; i++) {
_
next reply other threads:[~2004-03-16 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 16:49 mikem [this message]
2004-03-16 17:39 ` 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=20040316164922.GF21377@beardog.cca.cpqcorp.net \
--to=mikem@beardog.cca.cpqcorp.net \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.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®