From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] return number of devices claimed from acpi_bus_register_driver()
Date: Fri, 30 Jul 2004 19:17:34 +0200 [thread overview]
Message-ID: <20040730171734.GA29979@hell.org.pl> (raw)
In-Reply-To: <200407291209.28801.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Thus wrote Bjorn Helgaas:
> pnp_register_driver() and pci_register_driver() return the number of
> devices claimed by the driver. This makes acpi_bus_register_driver()
> do the same.
>
> All existing callers of acpi_bus_register_driver() either ignore the
> return value or check only for negative (error) return values.
I'd like to see that (or something similar) in if possible. The current
behaviour of acpi_bus_register_driver() does not allow for a clean solution
to back off in case no devices are claimed, thus most acpi drivers will
properly load even if there's no matching hardware available.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-07-30 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 18:09 [PATCH] return number of devices claimed from acpi_bus_register_driver() Bjorn Helgaas
[not found] ` <200407291209.28801.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-07-30 17:17 ` Karol Kozimor [this message]
2004-08-09 16:26 ` Len Brown
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=20040730171734.GA29979@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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