public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: [GIT PULL] Devicetree for 3.6
Date: Tue, 24 Jul 2012 16:01:40 -0500	[thread overview]
Message-ID: <500F0D34.6000907@gmail.com> (raw)

Linus,

While Grant's busy packing, please pull devicetree updates for 3.6.

Rob

The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:

  Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)

are available in the git repository at:

  git://sources.calxeda.com/kernel/linux.git tags/dt-for-3.6

for you to fetch changes up to e95d8aafa5d911bf523bc47fe89f3336eb8a1b51:

  of: mtd: nuke useless const qualifier (2012-07-10 10:32:06 -0500)

----------------------------------------------------------------
Devicetree updates for 3.6

A small set of changes for devicetree:
- Couple of Documentation fixes
- Addition of new helper function of_node_full_name
- Improve of_parse_phandle_with_args return values
- Some NULL related sparse fixes

----------------------------------------------------------------
Alexandre Courbot (1):
      of: return -ENOENT when no property

Artem Bityutskiy (1):
      of: mtd: nuke useless const qualifier

Grant Likely (1):
      devicetree: add helper inline for retrieving a node's full name

Marek Vasut (1):
      LED: Fix missing semicolon in OF documentation

Richard Genoud (1):
      usage-model.txt: fix typo machine_init->init_machine

Rob Herring (1):
      of: fix a few typos in the binding documentation

Sachin Kamat (1):
      of: Fix null pointer related warnings in base.c file

 Documentation/devicetree/bindings/gpio/led.txt     |    2 +-
 .../devicetree/bindings/mtd/partition.txt          |    2 +-
 Documentation/devicetree/usage-model.txt           |    2 +-
 arch/microblaze/pci/pci-common.c                   |    6 ++----
 arch/powerpc/kernel/pci-common.c                   |    6 ++----
 arch/powerpc/kernel/vio.c                          |    5 ++---
 arch/powerpc/platforms/cell/iommu.c                |    3 +--
 arch/powerpc/platforms/pseries/iommu.c             |    2 +-
 arch/sparc/kernel/of_device_64.c                   |    2 +-
 drivers/of/base.c                                  |   10 +++++-----
 drivers/of/irq.c                                   |    2 +-
 drivers/of/of_mtd.c                                |    2 +-
 include/linux/of.h                                 |   10 ++++++++++
 include/linux/of_mtd.h                             |    2 +-
 kernel/irq/irqdomain.c                             |    8 ++++----
 15 files changed, 34 insertions(+), 30 deletions(-)

             reply	other threads:[~2012-07-24 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 21:01 Rob Herring [this message]
2012-07-24 21:09 ` [GIT PULL] Devicetree for 3.6 Linus Torvalds

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=500F0D34.6000907@gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox