From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: mark.rutland@arm.com, balbi@ti.com, linux-usb@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
grant.likely@linaro.org, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, linux-sh@vger.kernel.org,
valentine.barshak@cogentembedded.com, rob@landley.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] phy-rcar-gen2-usb: add device tree support
Date: Thu, 06 Mar 2014 18:52:21 +0000 [thread overview]
Message-ID: <5318C3E5.10301@codethink.co.uk> (raw)
In-Reply-To: <5318CF02.80208@cogentembedded.com>
On 06/03/14 19:39, Sergei Shtylyov wrote:
> Hello.
>
> On 03/03/2014 07:44 PM, Felipe Balbi wrote:
>
>>> Add support of the device tree probing for the Renesas R-Car
>>> generation 2 SoCs
>>> documenting the device tree binding as necessary.
>
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
>> Unless someone on devicetree@vger gives me an ACK pretty soon, I'm
>> afraid this patch will miss v3.15.
>
> Mark, you've commented on v1 of the patch, I hope I cleared things
> up for you in my reply, how about an ACK (or at least new portion of
> comments)?
And whose patches are we going to use? :-p
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-03-06 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 1:07 [PATCH v2] phy-rcar-gen2-usb: add device tree support Sergei Shtylyov
2014-03-03 16:44 ` Felipe Balbi
2014-03-03 17:50 ` Sergei Shtylyov
2014-03-03 16:54 ` Felipe Balbi
2014-03-06 19:39 ` Sergei Shtylyov
2014-03-06 18:52 ` Ben Dooks [this message]
2014-03-07 5:46 ` Magnus Damm
2014-03-07 14:27 ` Sergei Shtylyov
2014-03-07 23:57 ` Sergei Shtylyov
2014-03-10 11:00 ` Magnus Damm
2014-03-11 23:32 ` Sergei Shtylyov
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=5318C3E5.10301@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=valentine.barshak@cogentembedded.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).