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  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:	Fri, 25 Jul 2014 08:08:27 -0700
From:	Doug Anderson <>
To:	Kukjin Kim <>,
	Andreas Färber <>
Cc:	linux-samsung-soc <>,
	Stephan van Schaik <>,
	Vincent Palatin <>,
	Ben Dooks <>,
	Rob Herring <>,
	Pawel Moll <>,
	Mark Rutland <>,
	Ian Campbell <>,
	Kumar Gala <>,
	Russell King <>,
	"moderated list:ARM/SAMSUNG ARM A..." 
	"open list:OPEN FIRMWARE AND..." <>,
	open list <>,
	Javier Martinez Canillas <>
Subject: Re: [PATCH v2 1/4] ARM: dts: exynos5250: max77686 is Snow only


On Thu, Jul 24, 2014 at 10:28 PM, Kukjin Kim <> 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 <>
>> ---
> Hi Andreas,
> I think this should be reviewed by chrome guys.
> Doug, can you have a look this series for exynos5250-chromebook?
> I'm not sure exynos5250-cros-common is still useful for exynos5250-spring...

Sorry, I've been on vacation and am now playing catchup.

Right.  The current suggestion is to rework to just duplicate things
and don't use exynos5250-cros-common.  I would structure the series

1. Fold the current exynos5250-cros-common directly into the snow
device tree file.

2. If desired, cleanup the snow device tree file.

3. Create the spring device tree file based on snow.  There will be
duplication, but so be it.  Please try to minimize diffs between the
snow ad spring device tree files.

4. If possible, identify "fragments" like "cros-ec-keyboard.dtsi" and
factor them out of both spring and snow device tree files.

You could certainly reorder some of the above steps if you wish (you
could split out fragments before creating the spring device tree, for

Please make sure to CC Javier (now on CC) since he's helping with
Chromebook upstreaming and he may have a lower latency in responding
than I do.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists