From: Valentine <valentine.barshak@cogentembedded.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-sh@vger.kernel.org, linux-ide@vger.kernel.org,
devicetree@vger.kernel.org, Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Kumar Gala <galak@codeaurora.org>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH V3 1/2] sata_rcar: Add R-Car Gen2 SATA PHY support
Date: Sat, 30 Nov 2013 00:35:52 +0400 [thread overview]
Message-ID: <5298FAA8.2050300@cogentembedded.com> (raw)
In-Reply-To: <20131129201406.GD21755@mtj.dyndns.org>
On 11/30/2013 12:14 AM, Tejun Heo wrote:
> Hello,
>
> On Wed, Nov 27, 2013 at 02:06:05AM +0400, Valentine wrote:
>> On 11/08/2013 04:09 PM, Valentine Barshak wrote:
>>
>> Tejun,
>> are you OK with taking this?
>
> Yeah, the stat part looks okay to me. How the two should be routed?
> Both through libata or should I just take the first one?
I'm not sure about that. I'm more concerned about the first one.
But I wouldn't mind if you take both.
>
> Thanks.
>
Thanks,
Val.
next prev parent reply other threads:[~2013-11-29 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 12:09 [PATCH V3 0/2] sata_rcar: Add Gen2 PHY support and document existing DT bindings Valentine Barshak
2013-11-08 12:09 ` [PATCH V3 1/2] sata_rcar: Add R-Car Gen2 SATA PHY support Valentine Barshak
2013-11-26 22:06 ` Valentine
2013-11-29 20:14 ` Tejun Heo
2013-11-29 20:35 ` Valentine [this message]
2013-11-29 20:42 ` Tejun Heo
2013-12-02 0:02 ` Simon Horman
2013-12-02 10:07 ` Valentine
2013-11-08 12:09 ` [PATCH V3 2/2] dt: Document sata_rcar bindings Valentine Barshak
2013-11-08 14:26 ` Kumar Gala
2013-11-08 14:30 ` Laurent Pinchart
2013-11-08 20:30 ` Valentine
2013-12-02 19:55 ` Tejun Heo
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=5298FAA8.2050300@cogentembedded.com \
--to=valentine.barshak@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@kernel.org \
--cc=vladimir.barinov@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).