From: Dave Jones <davej-bguaPGIxBblWITc6zSkvfdi2O/JbrIOy@public.gmane.org>
To: "Wang, Zhenyu Z" <zhenyu.z.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Li,
Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-acpi <linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Fu,
Michael" <michael.fu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Liu,
Bing Wei" <bing.wei.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/2] acpi_bus_register_driver conflict fix in acpi drivers
Date: Fri, 12 Nov 2004 06:37:44 +0000 [thread overview]
Message-ID: <20041112063744.GA19373@kernelslacker.org> (raw)
In-Reply-To: <9DE394C12A921946AEECE1F71944ECD58E4126@pdsmsx404>
On Fri, Nov 12, 2004 at 02:29:41PM +0800, Wang, Zhenyu Z wrote:
> This patch is accord with acpi_bus_register_driver return value fix.
> acpi driver won't cause any side effect if no device found to that
> driver.
> After this patch, output on my dell looks like:
> ACPI: AC [not found]
> ACPI: Asus_acpi [not found]
> ACPI: Battery [not found]
> ACPI: Power Button (FF) [PWRF]
> ACPI: Fan [not found]
> ACPI: Processor [CPU0] (supports C1)
> ACPI: Thermal [not found]
>
> which tell "not found" devices that acpi can't handle on that box.
Why on earth would we want to clutter the boot logs like this ?
ACPI is by far one of the most verbose subsystems already,
without making the problem worse.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-12 6:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 6:29 [PATCH 2/2] acpi_bus_register_driver conflict fix in acpi drivers Wang, Zhenyu Z
2004-11-12 6:37 ` Dave Jones [this message]
2004-11-12 6:39 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-11-12 6:45 Wang, Zhenyu Z
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=20041112063744.GA19373@kernelslacker.org \
--to=davej-bguapgixbblwitc6zskvfdi2o/jbrioy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bing.wei.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=michael.fu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=zhenyu.z.wang-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