From: "Zheng, Lv" <lv.zheng@intel.com>
To: Yisheng Xie <xieyisheng1@huawei.com>,
"Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"wmiles@sgl.com" <wmiles@sgl.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"guohanjun@huawei.com" <guohanjun@huawei.com>,
"wangxiongfeng2@huawei.com" <wangxiongfeng2@huawei.com>
Subject: RE: [PATCH] ACPICA: arm64: fix compile apci tools fail for arm64
Date: Mon, 24 Oct 2016 14:25:35 +0000 [thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886A257C05@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <b53fb761-0e7e-7864-2f4f-6aee84a8aba1@huawei.com>
Hi
> From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-owner@vger.kernel.org] On Behalf Of Yisheng
> Xie
> Subject: Re: [PATCH] ACPICA: arm64: fix compile apci tools fail for arm64
>
>
>
> On 2016/10/22 3:40, Zheng, Lv wrote:
> > Hi,
> >
> > I generated a solution with tools/power/acpi makefiles.
> > Please give it a try.
> Hi Lv,
> Your patch also works.
Thanks for the test.
I'll send it to the community for review.
Best regards
Lv
>
> > Sorry for the hackish build includes.
> >
> > Thanks and best regards
> > Lv
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-10-24 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 23:51 [PATCH] ACPICA: arm64: fix compile apci tools fail for arm64 Yisheng Xie
2016-10-17 22:26 ` Zheng, Lv
2016-10-18 11:46 ` Yisheng Xie
2016-10-18 22:07 ` Zheng, Lv
2016-10-20 1:45 ` Yisheng Xie
2016-10-20 18:42 ` Zheng, Lv
2016-10-21 19:40 ` Zheng, Lv
2016-10-24 8:01 ` Yisheng Xie
2016-10-24 14:25 ` Zheng, Lv [this message]
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=1AE640813FDE7649BE1B193DEA596E886A257C05@SHSMSX101.ccr.corp.intel.com \
--to=lv.zheng@intel.com \
--cc=devel@acpica.org \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=wangxiongfeng2@huawei.com \
--cc=wmiles@sgl.com \
--cc=xieyisheng1@huawei.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).