From: Will Deacon <will.deacon@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Sudeep Holla <Sudeep.Holla@arm.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>
Subject: Re: [PATCH 0/7] minor cleanups for ACPI processor driver
Date: Fri, 27 Mar 2015 14:40:15 +0000 [thread overview]
Message-ID: <20150327144014.GJ1562@arm.com> (raw)
In-Reply-To: <55156B28.9030802@linaro.org>
On Fri, Mar 27, 2015 at 02:37:28PM +0000, Hanjun Guo wrote:
> On 2015年03月27日 22:03, Will Deacon wrote:
> > Right now most maintainers are probably trying to stabilise their current
> > queues, so the most helpful thing you can do is test linux-next and send
> > fixes for any issues you find there.
>
> Sure, I will test linux-next on ARM64 platforms and x86 too.
Thanks.
> > It doesn't help that the series you posted seems to include two patch
> > series (n/7 and n/2).
>
> oh, side effects of staying up all night for the firmware mini-summit,
> please take those two patches for ARM64 ACPI if it is OK to you.
I already pushed them out :)
Have a good weekend,
Will
--
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
next prev parent reply other threads:[~2015-03-27 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 13:55 [PATCH 0/7] minor cleanups for ACPI processor driver Hanjun Guo
2015-03-27 13:55 ` [PATCH 1/7] ACPI / processor: remove cpu_index in acpi_processor_get_info() Hanjun Guo
2015-03-27 13:55 ` [PATCH 1/2] ARM64 / ACPI: Ignore the return error value of acpi_map_gic_cpu_interface() Hanjun Guo
2015-03-27 13:55 ` [PATCH 2/7] ACPI / processor: remove phys_id in acpi_processor_get_info() Hanjun Guo
2015-03-27 13:55 ` [PATCH 2/2] ARM64 / ACPI: make acpi_map_gic_cpu_interface() as void function Hanjun Guo
2015-03-27 13:55 ` [PATCH 3/7] ACPI / processor: Introduce invalid_logical_cpuid() Hanjun Guo
2015-03-27 13:55 ` [PATCH 4/7] Xen / ACPI / processor: use invalid_logical_cpuid() Hanjun Guo
2015-03-27 13:55 ` [PATCH 5/7] Xen / ACPI / processor: Remove unneeded NULL check in xen_acpi_processor_enable() Hanjun Guo
2015-03-27 13:55 ` [PATCH 6/7] ACPI / processor: return specific error instead of -1 Hanjun Guo
2015-03-27 13:55 ` [PATCH 7/7] ACPI / processor: Introduce invalid_phys_cpuid() Hanjun Guo
2015-03-27 14:01 ` [PATCH 0/7] minor cleanups for ACPI processor driver Hanjun Guo
2015-03-27 14:03 ` Will Deacon
2015-03-27 14:37 ` Hanjun Guo
2015-03-27 14:40 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-27 14:02 Hanjun Guo
2015-05-04 23:50 ` Rafael J. Wysocki
2015-05-05 1:10 ` 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=20150327144014.GJ1562@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hanjun.guo@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stefano.stabellini@eu.citrix.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).