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: <20150327140336.GG1562@arm.com>
Date:	Fri, 27 Mar 2015 14:03:36 +0000
From:	Will Deacon <will.deacon@....com>
To:	"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>
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

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?

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.

It doesn't help that the series you posted seems to include two patch
series (n/7 and n/2).

Will
--
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/