From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
francis.wiran@hp.com
Subject: Re: [PATCH] cpqarray update
Date: Mon, 26 Jan 2004 15:15:14 -0500 [thread overview]
Message-ID: <40157552.3040405@pobox.com> (raw)
In-Reply-To: <200401262002.i0QK2iAH031857@hera.kernel.org>
Linux Kernel Mailing List wrote:
> ChangeSet 1.1288, 2004/01/26 16:58:21-02:00, francis.wiran@hp.com
>
> [PATCH] cpqarray update
>
> Yes, we should. I usually ask Mike Miller in our group to send my
> patches since he's been doing that and more known in the community, but
> since you already got a hold of it ...yes, please :)
>
> CHANGELOG:
>
> * Fix for eisa card not detecting partitions properly
> * Use pci_module_init instead of pci_register_device to handle hotplug
> scenario and unregister if the driver can't find pci controller
> * Add BLKSSZGET ioctl
[...]
> @@ -616,7 +623,7 @@
>
> /* detect controllers */
> printk(DRIVER_NAME "\n");
> - pci_register_driver(&cpqarray_pci_driver);
> + pci_module_init(&cpqarray_pci_driver);
> cpqarray_eisa_detect();
>
> for(i=0; i< MAX_CTLR; i++) {
You need to check the return value of pci_module_init() for errors.
Jeff
next parent reply other threads:[~2004-01-26 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401262002.i0QK2iAH031857@hera.kernel.org>
2004-01-26 20:15 ` Jeff Garzik [this message]
2004-01-28 15:46 ` [PATCH] cpqarray update Hollis Blanchard
2004-01-28 17:40 ` Greg KH
2004-01-28 23:39 ` Jeff Garzik
2004-01-28 23:44 ` Jeff Garzik
2004-01-28 23:51 ` Greg KH
2004-01-26 22:32 Wiran, Francis
2004-01-27 1:51 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 4:48 Wiran, Francis
2004-01-27 4:50 Wiran, Francis
2004-01-28 22:53 Wiran, Francis
2004-01-28 23:10 Wiran, Francis
2004-01-28 23:28 ` Greg KH
2004-01-29 16:39 Wiran, Francis
2004-01-29 16:56 ` Jeff Garzik
2004-01-29 19:20 Wiran, Francis
2004-01-29 20:14 ` Jeff Garzik
2004-01-30 16:22 Wiran, Francis
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=40157552.3040405@pobox.com \
--to=jgarzik@pobox.com \
--cc=francis.wiran@hp.com \
--cc=linux-kernel@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