public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] ARM: dts: exynos: Prepare Spring
Date: Wed, 30 Jul 2014 16:17:10 +0200	[thread overview]
Message-ID: <53D8FE66.9050509@suse.de> (raw)
In-Reply-To: <1406728244-5105-1-git-send-email-afaerber@suse.de>

Am 30.07.2014 15:50, schrieb Andreas F?rber:
> Hello,
> 
> Based on the preinstalled 3.8 based ChromeOS kernel and previous 3.15 
> based attempts by Stephan and me that broke for 3.16, I've prepared a 
> device tree for the HP Chromebook 11 aka Google Spring.
> 
> v3 mainly does style cleanups, aligning Snow and Spring better.

And for your review convenience I attach the Snow vs. Spring diff.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 16746 AG N?rnberg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spring-snow.v3.diff
Type: text/x-patch
Size: 17407 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140730/a99e2600/attachment-0001.bin>

      parent reply	other threads:[~2014-07-30 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 13:50 [PATCH v3 0/4] ARM: dts: exynos: Prepare Spring Andreas Färber
2014-07-30 13:50 ` [PATCH v3 1/4] ARM: dts: Fix MMC pinctrl for exynos5250-snow Andreas Färber
2014-07-30 13:50 ` [PATCH v3 2/4] ARM: dts: Fold exynos5250-cros-common into exynos5250-snow Andreas Färber
2014-07-30 13:50 ` [PATCH v3 3/4] ARM: dts: Clean up exynos5250-snow Andreas Färber
2014-07-30 13:50 ` [PATCH v3 4/4] ARM: dts: Add exynos5250-spring device tree Andreas Färber
2014-07-31  9:26   ` Andreas Färber
2014-07-31  9:49     ` Ajay kumar
2014-07-31  9:53       ` Andreas Färber
2014-07-31 10:01         ` Ajay kumar
2014-07-30 14:17 ` Andreas Färber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53D8FE66.9050509@suse.de \
    --to=afaerber@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox