devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Murray <Andrew.Murray@arm.com>,
	"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, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC PATCH v2] of/pci: Provide support for parsing PCI DT ranges property
Date: Wed, 27 Mar 2013 13:55:37 +0100	[thread overview]
Message-ID: <20130327135537.52da5818@skate> (raw)
In-Reply-To: <CACRpkdZ_iuz96JWjHcr+6ugRY29MPA-wiGWtQQJqk30iTQE--Q@mail.gmail.com>

Dear Linus Walleij,

On Wed, 27 Mar 2013 13:50:09 +0100, Linus Walleij wrote:

> > Would it be possible to get this patch merged for 3.10, or get some
> > review comments that would allow us to rework it in time for 3.10 ?
> 
> Thomas can you supply a Reviewed-by/Tested-by tag?
> That certainly helps...

Yes, I'm planning on testing RFC v3 from Andrew right now, and send a
new version of the Marvell PCIe patch set that includes it. If all goes
well, should happen this afternoon.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-03-27 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 15:47 [RFC PATCH v2] of/pci: Provide support for parsing PCI DT ranges property Andrew Murray
2013-03-01  1:24 ` Linus Walleij
2013-03-20 20:05 ` Thomas Petazzoni
2013-03-27 12:50   ` Linus Walleij
2013-03-27 12:55     ` 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=20130327135537.52da5818@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=Andrew.Murray@arm.com \
    --cc=arnd@arndb.de \
    --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).