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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 16 Jan 2015 16:54:22 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Will Deacon <will.deacon@....com>
Cc:	Catalin Marinas <Catalin.Marinas@....com>,
	Jason Cooper <jason@...edaemon.net>,
	"grant.likely@...aro.org" <grant.likely@...aro.org>,
	"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	Mark Rutland <Mark.Rutland@....com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	"graeme.gregory@...aro.org" <graeme.gregory@...aro.org>,
	Sudeep Holla <Sudeep.Holla@....com>,
	"jcm@...hat.com" <jcm@...hat.com>,
	Marc Zyngier <Marc.Zyngier@....com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Rob Herring <robh@...nel.org>,
	Robert Richter <rric@...nel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Charles Garcia-Tobin <Charles.Garcia-Tobin@....com>,
	"phoenix.liyi@...wei.com" <phoenix.liyi@...wei.com>,
	Timur Tabi <timur@...eaurora.org>,
	"suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
	Yijing Wang <wangyijing@...wei.com>,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linaro-acpi <linaro-acpi@...ts.linaro.org>
Subject: Re: [PATCH v7 00/17] Introduce ACPI for ARM64 based on ACPI 5.1

On Fri, Jan 16, 2015 at 12:29:22PM +0000, Will Deacon wrote:
> On Fri, Jan 16, 2015 at 12:05:18PM +0000, Mark Brown wrote:

> > Actually, another thing that might help would be if you and/or Will were
> > to prod the relevant people for review, letting them know that the
> > controversy isn't likely to affect their bits.

> Hmm, we *could*, but having maintainers go round poking other people to
> review patches feels like the wrong way round to me. The authors should
> be taking ownership of this series and that's half of the problem we
> had in previous versions.

> It needs to be clear that Hanjun/Al/Graeme are the ones running the show,
> not just now, but (even more importantly) when people start building on
> top of the base support. If Catalin and I have to go around asking for
> review, it sets us off on the wrong foot imo.

That's true in general but equally right now it's also fairly clear that
this isn't going anywhere immediately (and one might assume potentially
may end up needing substantial rework) for arm64 related reasons which
creates a bit of stop energy that's more easily unblocked by the arm64
maintainers than others.  From that point of view I guess just giving
the ACPI folks something to point at to indicate that the remaining
issues on the architecture side aren't likely to affect the relevant
code would probably help also.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ