From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>
Cc: Lv Zheng <lv.zheng@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/3] ACPI: Integrate tools/power/acpi Makefile into tools Makefile.
Date: Wed, 15 Jan 2014 12:03:10 +0800 [thread overview]
Message-ID: <cover.1389676901.git.lv.zheng@intel.com> (raw)
In-Reply-To: <cover.1376378577.git.lv.zheng@intel.com>
This patchset updates tools/power/acpi folder to integrate its Makefiles
with other tools.
Lv Zheng (3):
ACPICA: acpidump: Cleanup tools/power/acpi makefiles.
ACPICA: acpidump: Enable tools Makefile to include acpi tools.
ACPICA: acpidump: Update MAINTAINERS file to include tools folder for
ACPI/ACPICA.
MAINTAINERS | 2 +
tools/Makefile | 16 ++-
tools/power/acpi/Makefile | 149 ++++++++++++++++++++--
tools/power/acpi/{ => man}/acpidump.8 | 0
tools/power/acpi/{ => tools/acpidump}/acpidump.c | 0
5 files changed, 152 insertions(+), 15 deletions(-)
rename tools/power/acpi/{ => man}/acpidump.8 (100%)
rename tools/power/acpi/{ => tools/acpidump}/acpidump.c (100%)
--
1.7.10
next parent reply other threads:[~2014-01-15 4:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1376378577.git.lv.zheng@intel.com>
2014-01-15 4:03 ` Lv Zheng [this message]
2014-01-15 4:04 ` [PATCH 1/3] ACPICA: acpidump: Cleanup tools/power/acpi makefiles Lv Zheng
2014-01-15 4:04 ` [PATCH 2/3] ACPICA: acpidump: Enable tools Makefile to include acpi tools Lv Zheng
2014-01-15 4:04 ` [PATCH 3/3] ACPICA: acpidump: Update MAINTAINERS file to include tools folder for ACPI/ACPICA Lv Zheng
2014-01-15 17:04 ` [PATCH 0/3] ACPI: Integrate tools/power/acpi Makefile into tools Makefile Al Stone
2014-01-15 21:43 ` Brown, Len
2014-01-15 21:48 ` Al Stone
2014-01-16 1:02 ` Zheng, Lv
2014-01-16 1:10 ` Rafael J. Wysocki
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=cover.1389676901.git.lv.zheng@intel.com \
--to=lv.zheng@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=zetalog@gmail.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).