From: Lin Ming <ming.m.lin@intel.com>
To: lenb <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Subject: ACPICA Release 20120420 linuxized patches
Date: Fri, 04 May 2012 09:16:39 +0800 [thread overview]
Message-ID: <1336094199.5520.56.camel@minggr> (raw)
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
Hi Len,
ACPICA Release 20120420 linuxized patches attached.
[PATCH 1/5] ACPICA: AML Parser: Fix two possible memory leaks in error path
[PATCH 2/5] ACPICA: Object dump routines: Use common function for string output
[PATCH 3/5] ACPICA: Lint fixes for acpi_write, no functional changes
[PATCH 4/5] ACPICA: Add support for multiple notify handlers
[PATCH 5/5] ACPICA: Update to version 20120420
Regards,
Lin Ming
[-- Attachment #2: acpica-v20120420.patch.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 8764 bytes --]
next reply other threads:[~2012-05-04 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 1:16 Lin Ming [this message]
2012-05-08 2:02 ` ACPICA Release 20120420 linuxized patches 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=1336094199.5520.56.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).