From: Len Brown <lenb@kernel.org>
To: linux-acpi@vger.kernel.org
Subject: ACPICA patches for Linux-2.6.38
Date: Wed, 12 Jan 2011 00:54:47 -0500 [thread overview]
Message-ID: <1294811696-19966-1-git-send-email-lenb@kernel.org> (raw)
Here is the ACPICA queue for 2.6.38.
Please let me know if you have troubles with any of them.
thanks,
Len Brown, Intel Open Source Technology Center
next reply other threads:[~2011-01-12 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 5:54 Len Brown [this message]
2011-01-12 5:54 ` [PATCH 1/9] ACPICA: Move GPE functions to new file evxfgpe.c Len Brown
2011-01-12 5:54 ` [PATCH 2/9] ACPICA: Rename some function and variable names Len Brown
2011-01-12 5:54 ` [PATCH 3/9] ACPICA: New GPE handler callback definition Len Brown
2011-01-12 5:54 ` [PATCH 4/9] ACPICA: Remove unused function declarations Len Brown
2011-01-12 5:54 ` [PATCH 5/9] ACPICA: Fix local variable mess in acpi_ev_asynch_execute_gpe_method Len Brown
2011-01-12 5:54 ` [PATCH 6/9] ACPICA: Implicit notify support Len Brown
2011-01-12 5:54 ` [PATCH 7/9] ACPICA: Global event handler Len Brown
2011-01-12 5:54 ` [PATCH 8/9] ACPICA: Misc comments to minimize code divergence Len Brown
2011-01-12 5:54 ` [PATCH 9/9] ACPICA: Update version to 20101209 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=1294811696-19966-1-git-send-email-lenb@kernel.org \
--to=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