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, 14 Jan 2015 13:17:08 +0100 From: Maxime Coquelin <maxime.coquelin@...com> To: David Miller <davem@...emloft.net>, <peter.griffin@...aro.org> Cc: <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <srinivas.kandagatla@...il.com>, <patrice.chotard@...com>, <peppe.cavallaro@...com>, <kishon@...com>, <arnd@...db.de>, <lee.jones@...aro.org>, <devicetree@...r.kernel.org>, <netdev@...r.kernel.org> Subject: Re: [PATCH v2 0/7] Fix sti drivers whcih mix reg address spaces Hi David, On 01/12/2015 12:54 AM, David Miller wrote: > From: Peter Griffin <peter.griffin@...aro.org> > Date: Wed, 7 Jan 2015 15:04:05 +0000 > >> A V2 of this old series incorporating Arnd and Lees Feedback form v1. >> >> Following on from Arnds comments about the picophy driver here >> https://lkml.org/lkml/2014/11/13/161, this series fixes the >> remaining upstreamed drivers for STI, which are mixing address spaces >> in the reg property. We do this in a way similar to the keystone >> and bcm7445 platforms, by having sysconfig phandle/ offset pair >> (where only one register is required). Or phandle / integer array >> where multiple offsets in the same bank are needed). >> >> This series breaks DT compatability! But the platform support >> is WIP and only being used by the few developers who are upstreaming >> support for it. I've made each change to the driver / dt doc / dt >> file as a single atomic commit so the kernel will remain bisectable. >> >> This series then also enables the picophy driver, and adds back in >> the ehci/ohci dt nodes for stih410 which make use of the picophy. > Series applied to net-next, thanks. Did you apply all the series to net-next? I need the DT patches in STi SoC tree, that will go to Linus tree via arm-soc, hopefully for v3.20. How could we synchronize? Maybe I could create an immutable tag on top of STi DT branch, which is based on top of v3.19-rc1, that you would merge in your tree? Please let me know your preferred way. Thanks, Maxime -- 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