public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 6/8] ARM: tegra: device tree changes
Date: Tue, 9 Apr 2013 17:04:08 +0200	[thread overview]
Message-ID: <201304091704.08446.arnd@arndb.de> (raw)
In-Reply-To: <1365181426-11547-6-git-send-email-swarren@wwwdotorg.org>

On Friday 05 April 2013, Stephen Warren wrote:
> Spam Status: Spamassassin 0% probability of being spam.
> 
> Full report:
> No, score=-4.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1  
> This branch contains the majority of the device tree changes for Tegra.
> Highlights include:
> 
> * Many changes for Tegra114, and the Dalmore board, to enable pinctrl,
>   SDHCI/MMC, PWM, DMA, I2C, KBC, SPI, battery, regulators.
> * Adding or enabling suspend wakeup sources on many boards, and adding
>   suspend timing parameters, to support the system suspend patches.
> * Adding clocks to the audio-related nodes, so that in 3.11, the audio
>   driver can pull these clocks from device tree rather than hard-coding
>   clock names.
> * Some small DT fixes/cleanup.
> 
> This branch is based on the previous clk pull request.

Hmm, I can't put this into the normal next/dt branch, since I really don't
want to add a dependency on the next/drivers branch there.

Can you send a replacement pull request that only contains the commits
that don't depend on that, and a separate request that can go on top
of next/drivers?

Alternatively, I could start a next/dt2 branch, but I'd like to avoid
that.

	Arnd

  reply	other threads:[~2013-04-09 15:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 17:03 [GIT PULL 1/8] ARM: tegra: DT-related fixes needed by the MMC tree Stephen Warren
2013-04-05 17:03 ` [GIT PULL 2/8] ARM: tegra: minor fixes Stephen Warren
2013-04-09 13:13   ` Arnd Bergmann
2013-04-05 17:03 ` [GIT PULL 3/8] ARM: tegra: cleanup Stephen Warren
2013-04-09 13:44   ` Arnd Bergmann
2013-04-09 15:36     ` Stephen Warren
2013-04-05 17:03 ` [GIT PULL 4/8] ARM: tegra: core SoC support development Stephen Warren
2013-04-09 14:37   ` Arnd Bergmann
2013-04-05 17:03 ` [GIT PULL 5/8] ARM: tegra: clock driver development Stephen Warren
2013-04-09 15:14   ` Arnd Bergmann
2013-04-09 15:38     ` Stephen Warren
2013-04-05 17:03 ` [GIT PULL 6/8] ARM: tegra: device tree changes Stephen Warren
2013-04-09 15:04   ` Arnd Bergmann [this message]
2013-04-09 15:55   ` Arnd Bergmann
2013-04-05 17:03 ` [GIT PULL 7/8] ARM: tegra: multi-platform conversion Stephen Warren
2013-04-09 14:59   ` Arnd Bergmann
2013-04-09 20:01     ` Arnd Bergmann
2013-04-09 21:49       ` Stephen Warren
2013-04-05 17:03 ` [GIT PULL 8/8] ARM: tegra: defconfig changes Stephen Warren
2013-04-09 15:16   ` Arnd Bergmann
2013-04-11 17:53     ` Olof Johansson
2013-04-09 11:01 ` [GIT PULL 1/8] ARM: tegra: DT-related fixes needed by the MMC tree Arnd Bergmann

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=201304091704.08446.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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