From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Harmony PCI-e and regulators
Date: Tue, 8 Mar 2011 10:06:28 -0800 [thread overview]
Message-ID: <AANLkTikZhz93EEjGov7MDa7tedMNvf05YavQD1ny2H8F@mail.gmail.com> (raw)
In-Reply-To: <cover.1299588456.git.mike@compulab.co.il>
Hi,
On Tue, Mar 8, 2011 at 4:58 AM, Mike Rapoport <mike@compulab.co.il> wrote:
> These patches provide update for Harmony PCI-e intialization and add
> registration of the TPS65862 PMIC.
> Additionally, there are several tegra_defconfig updates. These updates
> allow booting the Harmony with PCI-e enabled and add ability to boot
> TrimSlice with root on NFS.
>
> The patches were generated vs. Olof's board-for-next-i2c that seems to
> disappear. If there are now objection to these patches I can push them
> into separate branch in my tree, so that it can be pulled after Tegra
> I2C is merged.
Given the discussion yesterday, I merged what was essentially in the
-i2c branch into the regular boards-for-next branch. I can take these
through the same branch, since Colin hasn't pulled yet.
-Olof
prev parent reply other threads:[~2011-03-08 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 12:58 [PATCH 0/3] Harmony PCI-e and regulators Mike Rapoport
2011-03-08 12:58 ` [PATCH 1/3] ARM: tegra: harmony: update PCI-e initialization sequence Mike Rapoport
2011-03-08 12:58 ` [PATCH 2/3] ARM: tegra: harmony: initialize the TPS65862 PMIC Mike Rapoport
2011-03-08 13:15 ` Mark Brown
2011-03-09 7:41 ` Mike Rapoport
2011-03-09 10:15 ` Mark Brown
2011-03-09 11:53 ` Mike Rapoport
2011-03-09 12:22 ` Mark Brown
2011-03-09 13:19 ` Mike Rapoport
2011-03-09 13:15 ` Mark Brown
2011-03-09 13:23 ` Mike Rapoport
2011-03-08 22:12 ` Marc Dietrich
2011-03-09 6:23 ` Mike Rapoport
2011-03-09 11:14 ` Marvin
2011-03-08 12:58 ` [PATCH 3/3] ARM: tegra: update defconfig Mike Rapoport
2011-03-08 18:06 ` Olof Johansson [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=AANLkTikZhz93EEjGov7MDa7tedMNvf05YavQD1ny2H8F@mail.gmail.com \
--to=olof@lixom.net \
--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;
as well as URLs for NNTP newsgroup(s).