linux-kernel - Re: [PATCH 1/7] mfd: max8925: Move _IO resources out of ioport

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]

Date:	Wed, 8 Aug 2012 13:43:13 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>, linux-kernel@...r.kernel.org,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Russell King <rmk@....linux.org.uk>,
	"v3.4+" <stable@...r.kernel.org>
Subject: Re: [PATCH 1/7] mfd: max8925: Move _IO resources out of
 ioport_ioresource

On Tue, Aug 07, 2012 at 07:46:52PM +0000, Arnd Bergmann wrote:

> Thanks a lot for following through with this series! I would have
> preferred to have the second step in stable as Russell suggested,
> but since you did all the work, I'm not going to complain about it ;-)

Yeah, it'd be nicer to do it but given that the second step is adding a
new, non-bitmask resource type to a set of resource types that have
previously been all bitmasks I know I'd not get taken seriously
suggesting it as a fix to a system integrator without a big argument
about it and general unhappiness, most people doing stable releases I've
worked with would have a similar response.  It's not that it's unsafe,
it's that it sets off alarm bells and requires more due dilligence.
--
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/