From: Greg KH <greg@kroah.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
francis.wiran@hp.com
Subject: Re: [PATCH] cpqarray update
Date: Wed, 28 Jan 2004 09:40:52 -0800 [thread overview]
Message-ID: <20040128174052.GA6657@kroah.com> (raw)
In-Reply-To: <15D09760-51A9-11D8-AF96-000A95A0560C@us.ibm.com>
On Wed, Jan 28, 2004 at 09:46:06AM -0600, Hollis Blanchard wrote:
> On Jan 26, 2004, at 2:15 PM, Jeff Garzik wrote:
>
> >Linux Kernel Mailing List wrote:
> >>ChangeSet 1.1288, 2004/01/26 16:58:21-02:00, francis.wiran@hp.com
> >>@@ -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.
>
> I'm defining a new bus and had copied pci_module_init() to
> vio_module_init(). Here's what Greg KH had to say about that:
> >Eeek! I want to fix that code in pci_module_init() so it doesn't do
> >this at all. Please don't copy that horrible function. Just register
> >the driver with a call to vio_register_driver() and drop the whole
> >vio_module_init() completly. I'll be doing that for pci soon, and
> >there's no reason you want to duplicate this broken logic (you always
> >want your module probe to succeed, for lots of reasons...)
>
> So there's no need for the quoted patch hunk at all.
Well, changing it back to pci_register_driver() and actually checking
the return value would be a good idea :)
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-28 17:54 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 ` [PATCH] cpqarray update Jeff Garzik
2004-01-28 15:46 ` Hollis Blanchard
2004-01-28 17:40 ` Greg KH [this message]
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=20040128174052.GA6657@kroah.com \
--to=greg@kroah.com \
--cc=francis.wiran@hp.com \
--cc=hollisb@us.ibm.com \
--cc=jgarzik@pobox.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