From: Kishon Vijay Abraham I <kishon@ti.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
tj@kernel.org, devicetree@vger.kernel.org,
linux-ide@vger.kernel.org,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>
Subject: Re: [PATCH v4 2/4] Phy: Add a PHY driver for Marvell MVEBU SATA PHY.
Date: Sat, 11 Jan 2014 16:42:43 +0530 [thread overview]
Message-ID: <52D1272B.7050601@ti.com> (raw)
In-Reply-To: <20140110193130.GS19878@titan.lakedaemon.net>
Hi Jason,
On Saturday 11 January 2014 01:01 AM, Jason Cooper wrote:
> On Fri, Dec 27, 2013 at 10:03:22PM +0530, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Thursday 26 December 2013 10:55 PM, Andrew Lunn wrote:
>>> Kirkwood and Dove can turn the SATA phy on and off. Add a PHY driver
>>> to control this.
>>>
>>> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
>>> ---
>>> v1->v2:
>>> Use #defines instead of magic values
>>> select GENERIC_PHY in Kconfig.
>>>
>>> v3->v4
>>>
>>> Register phy_provider as the last step.
>>
>> The previous version is already sent to be merged. We can have the
>> new change merged in the rc cycle.
>
> Kishon,
>
> Looking at the patch dependencies, we'd like to keep the sata change in
> the same branch as the phy changes. Would you mind picking that one up
> and placing it in the same branch as the ones you already took? I have
PHY changes go in Greg's tree and he generally closes it ~2 weeks before
the start of merge window. So it's too late to go in PHY tree for this
merge window. Sorry.
Thanks
Kishon
next prev parent reply other threads:[~2014-01-11 11:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 20:21 [PATCH 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-17 20:21 ` [PATCH 2/4] Phy: Add a PHY driver for Marvell MVEBU SATA PHY Andrew Lunn
2013-12-19 10:40 ` Kishon Vijay Abraham I
2013-12-17 20:21 ` [PATCH 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2013-12-18 6:30 ` Kishon Vijay Abraham I
2013-12-18 12:13 ` Tejun Heo
2013-12-19 19:10 ` Andrew Lunn
2013-12-19 19:42 ` Tejun Heo
2013-12-26 17:25 ` [PATCH v4 0/4] PHY Driver for Marvell SATA Andrew Lunn
2013-12-26 17:25 ` [PATCH v4 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-26 17:25 ` [PATCH v4 2/4] Phy: Add a PHY driver for Marvell MVEBU SATA PHY Andrew Lunn
2013-12-27 16:33 ` Kishon Vijay Abraham I
2014-01-10 19:31 ` Jason Cooper
2014-01-11 11:12 ` Kishon Vijay Abraham I [this message]
2013-12-26 17:25 ` [PATCH v4 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2014-01-20 12:47 ` Tejun Heo
2013-12-26 17:25 ` [PATCH v4 4/4] Phy: Add DT nodes on kirkwood and Dove for the SATA PHY Andrew Lunn
[not found] ` <52B140F2.8070900-l0cyMroinI0@public.gmane.org>
2013-12-19 19:03 ` [PATCH 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2013-12-20 3:25 ` Jason Cooper
2013-12-17 20:21 ` [PATCH 4/4] Phy: Add DT nodes on kirkwood and Dove for the SATA PHY Andrew Lunn
2013-12-18 6:32 ` Kishon Vijay Abraham I
2013-12-22 17:21 ` Jason Cooper
2013-12-17 20:27 ` [PATCH 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-20 3:21 ` Jason Cooper
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=52D1272B.7050601@ti.com \
--to=kishon@ti.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-ide@vger.kernel.org \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=tj@kernel.org \
/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).