All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	Stephen Warren <swarren@nvidia.com>,
	Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: [GIT PULL] DT fixes for 3.5
Date: Tue, 03 Jul 2012 21:40:39 -0500	[thread overview]
Message-ID: <4FF3AD27.5070901@gmail.com> (raw)
In-Reply-To: <4FDA9261.2070208@gmail.com>

Linus,

On 06/14/2012 08:39 PM, Rob Herring wrote:
> Grant,
> 
> Please pull. Mainly some documentation updates and 2 fixes:
> 
> - An export symbol fix for of_platform_populate from Stephen W.
> - A fix for the order compatible entries are matched to ensure the
> first compatible string is matched when there are multiple matches.
> 

As Grant is offline the next month or two, can you please pull these
fixes for device tree for 3.5.

Rob

> The following changes since commit cfaf025112d3856637ff34a767ef785ef5cf2ca9:
> 
>   Linux 3.5-rc2 (2012-06-08 18:40:09 -0700)
> 
> are available in the git repository at:
> 
>   git://sources.calxeda.com/kernel/linux.git fixes-for-grant
> 
> for you to fetch changes up to 107a84e61cdd3406c842a0e4be7efffd3a05dba6:
> 
>   of: match by compatible property first (2012-06-14 20:29:40 -0500)
> 
> ----------------------------------------------------------------
> Fabio Estevam (5):
>       dt: fsl-imx-cspi.txt: Fix comment about GPIOs used for chip selects
>       dt: fsl-imx-esdhc.txt: Fix gpio number assignment
>       dt: fsl-mma8450.txt: Add missing 'reg' description
>       dt: fsl-fec.txt: Fix gpio number assignment
>       dt: mc13xxx.txt: Fix gpio number assignment
> 
> Stephen Warren (1):
>       of: export of_platform_populate()
> 
> Thierry Reding (2):
>       of: Add Avionic Design vendor prefix
>       of: match by compatible property first
> 
>  .../devicetree/bindings/input/fsl-mma8450.txt      |    1 +
>  Documentation/devicetree/bindings/mfd/mc13xxx.txt  |    4 +--
>  .../devicetree/bindings/mmc/fsl-imx-esdhc.txt      |    4 +--
>  Documentation/devicetree/bindings/net/fsl-fec.txt  |    2 +-
>  .../devicetree/bindings/spi/fsl-imx-cspi.txt       |    4 +--
>  .../devicetree/bindings/vendor-prefixes.txt        |    1 +
>  drivers/of/base.c                                  |   30
> +++++++++++++++++---
>  drivers/of/platform.c                              |    1 +
>  8 files changed, 36 insertions(+), 11 deletions(-)
> 



  parent reply	other threads:[~2012-07-04  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15  1:39 [GIT PULL] DT fixes for 3.5 Rob Herring
2012-06-15  1:39 ` Rob Herring
2012-06-26 23:38 ` Rob Herring
2012-06-26 23:38   ` Rob Herring
2012-06-27  0:34   ` Stephen Warren
2012-06-27  0:34     ` Stephen Warren
2012-07-04  2:40 ` Rob Herring [this message]
2012-07-04  2:40   ` Rob Herring

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=4FF3AD27.5070901@gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=fabio.estevam@freescale.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=thierry.reding@avionic-design.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.