From: Hanjun Guo <guohanjun@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Hanjun Guo <hanjun.guo@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
linaro-acpi@lists.linaro.org, Sudeep Holla <Sudeep.Holla@arm.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Tony Luck <tony.luck@intel.com>, Lv Zheng <lv.zheng@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Grant Likely <grant.likely@linaro.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ACPI / processor: Update the comments in processor.h
Date: Wed, 26 Nov 2014 09:20:08 +0800 [thread overview]
Message-ID: <54752AC8.70309@huawei.com> (raw)
In-Reply-To: <2001637.yVyNT03Tcn@vostro.rjw.lan>
On 2014/11/26 7:13, Rafael J. Wysocki wrote:
> On Thursday, October 30, 2014 05:52:58 PM Hanjun Guo wrote:
>> In commit 46ba51e (ACPI / processor: Introduce ARCH_MIGHT_HAVE_ACPI_PDC),
>> acpi_processor_set_pdc() was moved to processor_pdc.c, so update
>> the comments accordingly.
>>
>> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> Patches [2-3/3] from this set need to be rebased on top of current linux-next
> and resent, sorry about that.
No problem. I will rebase and resend today.
Thanks
Hanjun
prev parent reply other threads:[~2014-11-26 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:52 [PATCH 1/3] ACPI / processor: Update the comments in processor.h Hanjun Guo
2014-10-30 9:52 ` [PATCH 2/3] ACPI / processor: Convert apic_id to phys_id to make it arch agnostic Hanjun Guo
2014-10-30 9:53 ` [PATCH 3/3] ACPI / processor: Rename acpi_(un)map_lsapic() to acpi_(un)map_cpu() Hanjun Guo
2014-10-30 20:12 ` Rafael J. Wysocki
2014-10-30 23:49 ` Hanjun Guo
2014-10-31 22:55 ` Rafael J. Wysocki
2014-11-14 23:35 ` Rafael J. Wysocki
2014-11-17 2:31 ` Hanjun Guo
2014-11-25 23:13 ` [PATCH 1/3] ACPI / processor: Update the comments in processor.h Rafael J. Wysocki
2014-11-26 1:20 ` Hanjun Guo [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=54752AC8.70309@huawei.com \
--to=guohanjun@huawei.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=grant.likely@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@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).