From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Andrew Murray <andrew.murray@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
Thierry Reding <thierry.reding@avionic-design.de>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: [RFC PATCH RESEND v2] of/pci: Provide support for parsing PCI DT ranges property
Date: Fri, 22 Mar 2013 10:49:17 +0100 [thread overview]
Message-ID: <20130322104917.78e98b93@skate> (raw)
In-Reply-To: <20130322093936.GA875@arm.com>
Andrew,
On Fri, 22 Mar 2013 09:39:36 +0000, Andrew Murray wrote:
> > Thanks, I've tested this successfully with the Marvell PCIe driver. I'm
> > about to send a new version of the Marvell PCIe patch set that includes
> > this RFC proposal.
> >
> > I only made two small changes compared to your version, detailed below.
>
> Thanks for the feedback, all looks good to me. Do I need to give ack?
If you could ack the version I sent in the PCIe patch set yesterday, it
would be great yes.
I'm hoping also that Grant will have a look at this and say if he
agrees. The entire PCIe patch set depends on this patch, so if any
rework of this OF patch needs to be done, it'd be great to know it
sooner rather than later.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-22 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 12:23 [RFC PATCH RESEND v2] of/pci: Provide support for parsing PCI DT ranges property Andrew Murray
2013-03-01 15:13 ` Rob Herring
2013-03-06 9:42 ` Andrew Murray
2013-03-08 16:39 ` Andrew Murray
2013-03-21 16:06 ` Thomas Petazzoni
2013-03-22 9:39 ` Andrew Murray
2013-03-22 9:49 ` Thomas Petazzoni [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=20130322104917.78e98b93@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=Liviu.Dudau@arm.com \
--cc=andrew.murray@arm.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=thierry.reding@avionic-design.de \
/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).