From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/5] PCI: tegra: Overhaul regulator usage
Date: Thu, 29 May 2014 11:48:45 -0600 [thread overview]
Message-ID: <538772FD.40407@wwwdotorg.org> (raw)
In-Reply-To: <1401288555-24197-2-git-send-email-thierry.reding@gmail.com>
On 05/28/2014 08:49 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The current usage of regulators for the Tegra PCIe block is wrong. It
> doesn't accurately reflect the actual supply inputs of the IP block and
> therefore isn't as flexible as it should be. Rectify this by describing
> all possible supply inputs in the device tree binding documentation and
> deprecate the old supply properties.
The series looks fine to me at a quick glance. Since Bjorn has ack'd the
PCIe driver patch, I'll apply this to the Tegra tree for 3.17. I'll put
it into a topic branch in case it needs to be merged into the PCI tree
to resolve any conflicts.
next prev parent reply other threads:[~2014-05-29 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 14:49 [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage Thierry Reding
2014-05-28 14:49 ` [PATCH v2 1/5] " Thierry Reding
2014-05-29 17:48 ` Stephen Warren [this message]
2014-05-28 14:49 ` [PATCH v2 2/5] ARM: tegra: Add new PCIe regulator properties Thierry Reding
2014-05-28 14:49 ` [PATCH v2 3/5] PCI: tegra: Implement accurate power supply scheme Thierry Reding
2014-05-28 14:49 ` [PATCH v2 4/5] PCI: tegra: Remove deprecated power supply properties Thierry Reding
2014-05-28 14:49 ` [PATCH v2 5/5] ARM: tegra: Remove legacy PCIe " Thierry Reding
2014-06-16 18:30 ` [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage Stephen Warren
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=538772FD.40407@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).