From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: [PATCH 0/3] ACPI autoload (v2)
Date: Mon, 23 Jul 2007 14:43:20 +0200 [thread overview]
Message-ID: <1185194600.14451.43.camel@fanta4.site> (raw)
Hi Len,
I rebased my patches against your recent commits.
Changes to previous patch(es):
- forgot fixed button hids in button.c
- adjusted linux specific hids to your suggestions (e.g. LNXVIDEO)
- renamed acpi_device_id to acpica_device_id
(instead __acpi_device_id)
- removed some unneeded comments
It would be great to still see this in 2.6.23.
If you have concerns about this, please let me know soon, as we then
need more ugly workarounds in userspace to get all ACPI modules loaded.
Kay: On the second patch I added your signed-off. IIRC you said this is
ok. Thanks a lot for your testing, review, suggestions, enhancements and
cleanups here.
Thomas
next reply other threads:[~2007-07-23 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 12:43 Thomas Renninger [this message]
2007-07-23 13:34 ` [PATCH 0/3] ACPI autoload (v2) Kay Sievers
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=1185194600.14451.43.camel@fanta4.site \
--to=trenn@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@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