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
| ||
|
Date: Wed, 9 Dec 2015 13:35:00 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Mark Brown <broonie@...nel.org> Cc: "Andrew F. Davis" <afd@...com>, Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Kumar Gala <galak@...eaurora.org>, Alexandre Courbot <gnurou@...il.com>, Samuel Ortiz <sameo@...ux.intel.com>, Liam Girdwood <lgirdwood@...il.com>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support On Tue, Dec 8, 2015 at 8:16 PM, Mark Brown <broonie@...nel.org> wrote: > On Mon, Dec 07, 2015 at 01:58:47PM -0600, Andrew F. Davis wrote: > >> As all of this driver should be taken though the MFD tree how >> can this gpiolib change be handled? If we have gpio.parent it >> will not build on MFD, with gpio.dev it will fail to build when >> the changes are merged from the gpio subsystem. As the change >> has not been merged into linux-next as far a I can tell maybe >> this should be taken as is, then when the gpiolib change is >> made this can be changed with all the other drivers? > > Do a cross tree merge in one direction or the other between MFD and GPIO. If Lee makes an immutable branch with this stuff on it I can pull that in and put a fix on top of it (like I recently did with the ASoC AC97 codec). I have "only" renamed the .dev field of struct gpio_chip to .parent but I'm bombing out another 150 or so patches today, ridding all GPIO drivers in the kernel of container_of(). A bit painful but nothing to what tglx has gone through for refactoring IRQ chips... Yours, Linus Walleij -- 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/
Powered by blists - more mailing lists