From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ACPI / processor: Rename acpi_(un)map_lsapic() to acpi_(un)map_cpu()
Date: Mon, 17 Nov 2014 10:31:01 +0800 [thread overview]
Message-ID: <54695DE5.2080309@linaro.org> (raw)
In-Reply-To: <1820875.eppNBckBcQ@vostro.rjw.lan>
On 2014-11-15 7:35, Rafael J. Wysocki wrote:
> On Friday, October 31, 2014 11:55:46 PM Rafael J. Wysocki wrote:
>> On Friday, October 31, 2014 07:49:49 AM Hanjun Guo wrote:
>>> On 2014?10?31? 04:12, Rafael J. Wysocki wrote:
>>>> On Thursday, October 30, 2014 05:53:00 PM Hanjun Guo wrote:
>>>>> acpi_map_lsapic() will allocate a logical CPU number and map it to
>>>>> physical CPU id (such as APIC id) for the hot-added CPU, it will also
>>>>> do some mapping for NUMA node id and etc, acpi_unmap_lsapic() will
>>>>> do the reverse.
>>>>>
>>>>> We can see that the name of the function is a little bit confusing and
>>>>> arch dependent so rename them as acpi_(un)map_map() to make arch
>>>>
>>>> That's acpi_(un)map_cpu() I guess?
>>>
>>> ah, yes, typos, it should be acpi_(un)map_cpu(), my fault.
>>> should I send another version?
>>
>> No, I can fix this up.
>
> I've queued up the series for 3.19, thanks!
Thanks!
Hanjun
next prev parent reply other threads:[~2014-11-17 2:31 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 [this message]
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
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=54695DE5.2080309@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).