linux-kernel - Re: [PATCH 0/7] minor cleanups for ACPI processor driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55156B28.9030802@linaro.org>
Date:	Fri, 27 Mar 2015 22:37:28 +0800
From:	Hanjun Guo <hanjun.guo@...aro.org>
To:	Will Deacon <will.deacon@....com>
CC:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Catalin Marinas <Catalin.Marinas@....com>,
	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	Sudeep Holla <Sudeep.Holla@....com>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>
Subject: Re: [PATCH 0/7] minor cleanups for ACPI processor driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/