From: Jes Sorensen <jes@sgi.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>,
jesper.juhl@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: initcall at ... returned with error code -19 (Was: Re: 2.6.16-rc5-mm2)
Date: Tue, 07 Mar 2006 18:30:59 +0100 [thread overview]
Message-ID: <440DC353.8080101@sgi.com> (raw)
In-Reply-To: <200603071031.32558.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> On Tuesday 07 March 2006 06:10, Jes Sorensen wrote:
>> I'd subscribe to that. It seems a bit wrong to return 0 in a
>> loadable module if nothing is found, and some of the ones people have
>> posted patches for converting can be either modules or static.
>
> Yeah, maybe. But it feels a little like the question of whether
> {pci,pnp,acpi_bus}_register_driver() should return the number of
> devices found. The consensus is that these functions should return
> only a negative error, or zero for success, leaving any counting of
> devices to the driver's .probe() or .add() method.
>
> I think a loadable driver's init function *should* return success
> even if no device is yet present. Maybe you want to load the driver
> before hot-adding the device.
I don't really like this ;-( If a driver is loaded for a specific PCI
device and that isn't present, then IMHO it is better to have it
return -ENODEV and unload it again.
Cheers,
Jes
next prev parent reply other threads:[~2006-03-07 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 21:59 initcall at ... returned with error code -19 (Was: Re: 2.6.16-rc5-mm2) Jesper Juhl
2006-03-06 22:08 ` Andrew Morton
2006-03-06 22:13 ` Jesper Juhl
2006-03-07 1:09 ` Paul Jackson
2006-03-07 13:10 ` Jes Sorensen
2006-03-07 17:31 ` Bjorn Helgaas
2006-03-07 17:30 ` Jes Sorensen [this message]
2006-03-06 22:16 ` Randy.Dunlap
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=440DC353.8080101@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.