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, 29 Mar 2017 21:48:48 +0200 From: Arnd Bergmann <arnd@...db.de> To: Geert Uytterhoeven <geert+renesas@...der.be> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Kevin Hilman <khilman@...nel.org>, Magnus Damm <magnus.damm@...il.com>, Olof Johansson <olof@...om.net>, Simon Horman <horms@...ge.net.au>, Linux-Renesas <linux-renesas-soc@...r.kernel.org>, Linux ARM <linux-arm-kernel@...ts.infradead.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2 0/2] base: soc: soc_device_match() improvements On Wed, Mar 29, 2017 at 9:38 PM, Geert Uytterhoeven <geert+renesas@...der.be> wrote: > Hi Arnd, Greg, Kevin, Magnus, Olof, Simon, > > This patch series contains two improvements for the SoC bus and > soc_device_match(). The second one is a dependency for handling > different SoC revisions in the Renesas R-Car SYSC driver, which manages > PM Domains and thus needs to be initialized from an early_initcall[*]. > > Changes compared to v1: > - Drop RFC state, > - Add more explanation, > - Add Acked-by. > > Due to the dependency, and as changes for the Renesas R-Car SYSC driver > typically go in through the renesas and arm-soc trees, and if you agree, > I would like to send a pull request for these changes, to be pulled by > all of the driver core, renesas, and arm-soc trees. This is similar to > how soc_device_match() was integrated earlier. > Then the Renesas R-Car SYSC driver changes can easily be queued on top > in the renesas tree afterwards. > > Do you agree? > Thanks for your answer! Merging this through arm-soc is fine with me. > P.S. If you think it's already too late in the cycle to queue Renesas > R-Car SYSC driver changes for v4.12 on top, please say so. Then the > dependency is relaxed, and this series can just go in through the > driver core tree, with the Renesas part to follow for v4.13. We can take it for 4.12. Arnd
Powered by blists - more mailing lists