From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932149AbbC0Ohy (ORCPT ); Fri, 27 Mar 2015 10:37:54 -0400 Received: from mail-pd0-f170.google.com ([209.85.192.170]:35922 "EHLO mail-pd0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932118AbbC0Ohs (ORCPT ); Fri, 27 Mar 2015 10:37:48 -0400 Message-ID: <55156B28.9030802@linaro.org> Date: Fri, 27 Mar 2015 22:37:28 +0800 From: Hanjun Guo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Will Deacon CC: "Rafael J. Wysocki" , Catalin Marinas , Boris Ostrovsky , Stefano Stabellini , Lorenzo Pieralisi , Sudeep Holla , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linaro-acpi@lists.linaro.org" Subject: Re: [PATCH 0/7] minor cleanups for ACPI processor driver References: <1427464513-14414-1-git-send-email-hanjun.guo@linaro.org> <20150327140336.GG1562@arm.com> In-Reply-To: <20150327140336.GG1562@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Will, On 2015年03月27日 22:03, Will Deacon wrote: > Hanjun, > > On Fri, Mar 27, 2015 at 01:55:04PM +0000, Hanjun Guo wrote: >> This patch set are some minor cleanups for ACPI processor driver >> to address the comments which raised by Rafael in ARM64 ACPI core >> patches, so this patch set is on top of ARM64 ACPI core patches >> the git tree is >> >> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git >> branch for-next/acpi. >> >> Rafael, I assume this patchset will be taken with your tree if >> it makes sense, any rebase work needed please let me know. >> >> the last patch - ACPI / processor: Introduce invalid_phys_cpuid() >> will cut u64 mpidr to int, but I think it is ok for error values, >> correct me if I'm wrong. > > I appreciate that you probably have a bunch of code building on top of > the series that's in linux-next, but sending it out at the moment is > hugely confusing -- particularly when this is targetting an independent > tree. If you have patches for 4.2, please can you wait until after the > merge window before posting for review? OK, thanks for the reminding, I didn't mean any confusion but actually I did, sorry for that. > > 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. > > 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. Thanks Hanjun