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: Fri, 25 Jul 2014 17:30:12 +0200 From: Andreas Färber <afaerber@...e.de> To: Doug Anderson <dianders@...omium.org> CC: Kukjin Kim <kgene.kim@...sung.com>, linux-samsung-soc <linux-samsung-soc@...r.kernel.org>, Stephan van Schaik <stephan@...khronix.com>, Vincent Palatin <vpalatin@...omium.org>, Ben Dooks <ben-linux@...ff.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>, Russell King <linux@....linux.org.uk>, "ARM/SAMSUNG ARM A..." <linux-arm-kernel@...ts.infradead.org>, "OPEN FIRMWARE AND..." <devicetree@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Javier Martinez Canillas <javier.martinez@...labora.co.uk> Subject: Re: [PATCH v2 1/4] ARM: dts: exynos5250: max77686 is Snow only Hi Doug, Am 25.07.2014 17:13, schrieb Doug Anderson: > On Fri, Jul 25, 2014 at 8:08 AM, Doug Anderson <dianders@...omium.org> wrote: >> On Thu, Jul 24, 2014 at 10:28 PM, Kukjin Kim <kgene.kim@...sung.com> wrote: >>> Andreas Färber wrote: >>>> >>>> Move it from exynos5250-cros-common.dtsi to exynos5250-snow.dts. >>>> Spring does not need it, it uses an s5m8767 instead. >>>> >>>> Signed-off-by: Andreas Färber <afaerber@...e.de> >>>> --- >>> >>> Doug, can you have a look this series for exynos5250-chromebook? >>> I'm not sure exynos5250-cros-common is still useful for exynos5250-spring... >> >> Right. The current suggestion is to rework to just duplicate things >> and don't use exynos5250-cros-common. > > Oh, it actually looks like your patch series ends up there, but the > first patch confused me. NP, guess you just started reading in the middle. ;) > Why move just the maxim PMIC first? Review of the movements surely is easier this way, and it did not yet seem a done deal that we would drop -cros-common. The merge patch nicely shows which common parts need to be copied into spring. > Move > everything at once and be done with the common file, then do > cleanup... If everyone agrees that we want to proceed that way, we can easily squash patches 1+2. Separating is always harder. Cheers, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- 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