From: Kishon Vijay Abraham I <kishon@ti.com>
To: Maxime Coquelin <maxime.coquelin@st.com>,
Lee Jones <lee.jones@linaro.org>,
Kishon Vijay Abraham I <kishon@uda0393678>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infrared.org>, <kernel@stlinux.com>
Subject: Re: [STLinux Kernel] [PATCH v3 0/5] phy: miphy365x: Introduce support for MiPHY365x
Date: Wed, 23 Jul 2014 13:54:45 +0530 [thread overview]
Message-ID: <53CF714D.5090503@ti.com> (raw)
In-Reply-To: <53CF6B35.30707@st.com>
On Wednesday 23 July 2014 01:28 PM, Maxime Coquelin wrote:
> Hi Kishon,
>
> On 07/22/2014 09:23 AM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Monday 21 July 2014 01:09 PM, Lee Jones wrote:
>>> Hi Kishon,
>>>
>>>>> This patchset is based on the two core patches you sent to the
>>>>> list which facilitate creating PHYs residing on multi-channel
>>>>> controllers. The changes since the last submission centre
>>>>> around dynamic PHY creation based solely on what is provided via
>>>>> Device Tree, as requested. The other review comments have also
>>>>> been addressed in this set.
>>>>
>>>> Merged the first four patches of this series. (merged v3+1 for 1st patch).
>>>> I'm not sure who would be merging the dt patch (5/5). But for now I've merged
>>>> 2/5 in linux-phy tree since the phy patch seems to be dependent on it.
>>>> So the dt patch can be merged only after -rc1. However if whoever merges
>>>> dt wants to get it merged during the merge window, I can prepare a common
>>>> branch which both of us can merge to. Either ways, dt Maintainer should
>>>> let me know.
>>>
>>> Thanks for applying. It would be really helpful if you could put just
>>> patch 2/5 onto an immutable branch and provide a tag e that Maxime
>>> could pull from.
>>
>> Sure. Created tag
>> git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git
>> miphy365x_dt_common_header (branch:miphy365x_dt_header). It is based on 3.16-rc5.
>
> Merged into git://git.stlinux.com/devel/kernel/linux-sti.git sti-dt-for-v3.17-1
cool, thanks.
-Kishon
>
> Thanks!
> Maxime
>
>>
>> Thanks
>> Kishon
>>>
>>> Kind regards,
>>> Lee
>>>
>>>>> .../devicetree/bindings/phy/phy-miphy365x.txt | 76 +++
>>>>> arch/arm/boot/dts/stih416-b2020-revE.dts | 10 +
>>>>> arch/arm/boot/dts/stih416-b2020.dts | 12 +
>>>>> arch/arm/boot/dts/stih416.dtsi | 22 +
>>>>> drivers/phy/Kconfig | 10 +
>>>>> drivers/phy/Makefile | 1 +
>>>>> drivers/phy/phy-miphy365x.c | 636 +++++++++++++++++++++
>>>>> include/dt-bindings/phy/phy-miphy365x.h | 14 +
>>>>> 8 files changed, 781 insertions(+)
>>>
>>
>> _______________________________________________
>> Kernel mailing list
>> Kernel@stlinux.com
>> http://www.stlinux.com/mailman/listinfo/kernel
>>
prev parent reply other threads:[~2014-07-23 8:25 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 11:41 [PATCH v3 0/5] phy: miphy365x: Introduce support for MiPHY365x Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-09 11:41 ` [PATCH v3 1/5] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-09 14:30 ` Gabriel Fernandez
2014-07-09 14:30 ` Gabriel Fernandez
2014-07-09 16:37 ` Lee Jones
2014-07-09 16:37 ` Lee Jones
2014-07-10 9:09 ` [PATCH v3+1 " Lee Jones
2014-07-10 9:09 ` Lee Jones
2014-07-09 11:41 ` [PATCH v3 2/5] phy: miphy365x: Add MiPHY365x header file for DT x Driver defines Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-11 9:07 ` Gabriel Fernandez
2014-07-11 9:07 ` Gabriel Fernandez
2014-07-11 9:33 ` Lee Jones
2014-07-11 9:33 ` Lee Jones
2014-07-09 11:41 ` [PATCH v3 3/5] phy: miphy365x: Provide support for the MiPHY356x Generic PHY Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-11 9:07 ` Gabriel Fernandez
2014-07-11 9:07 ` Gabriel Fernandez
2014-07-09 11:41 ` [PATCH v3 4/5] phy: miphy365x: Represent each PHY channel as a DT subnode Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-09 11:41 ` [PATCH v3 5/5] ARM: DT: STi: STiH416: Add DT node for MiPHY365x Lee Jones
2014-07-09 11:41 ` Lee Jones
2014-07-11 11:54 ` [PATCH v3+1 " Lee Jones
2014-07-11 11:54 ` Lee Jones
2014-07-12 0:30 ` Sergei Shtylyov
2014-07-12 0:30 ` Sergei Shtylyov
2014-07-14 7:58 ` Lee Jones
2014-07-14 7:58 ` Lee Jones
2014-07-20 17:56 ` Sergei Shtylyov
2014-07-20 17:56 ` Sergei Shtylyov
2014-07-22 9:02 ` [STLinux Kernel] " Maxime Coquelin
2014-07-22 9:02 ` Maxime Coquelin
2014-07-09 14:52 ` [PATCH v3 0/5] phy: miphy365x: Introduce support " Kishon Vijay Abraham I
2014-07-09 14:52 ` Kishon Vijay Abraham I
2014-07-10 15:35 ` [STLinux Kernel] " Peter Griffin
2014-07-10 15:35 ` Peter Griffin
2014-07-11 10:31 ` Lee Jones
2014-07-11 10:31 ` Lee Jones
2014-07-11 11:05 ` Peter Griffin
2014-07-11 11:05 ` Peter Griffin
2014-07-11 11:13 ` Kishon Vijay Abraham I
2014-07-11 11:13 ` Kishon Vijay Abraham I
2014-07-11 11:34 ` Lee Jones
2014-07-11 11:34 ` Lee Jones
2014-07-11 11:30 ` Lee Jones
2014-07-11 11:30 ` Lee Jones
2014-07-11 11:33 ` Maxime Coquelin
2014-07-11 11:33 ` Maxime Coquelin
2014-07-11 11:38 ` Lee Jones
2014-07-11 11:38 ` Lee Jones
[not found] ` <20140721062805.GA8781@uda0393678>
2014-07-21 7:39 ` Lee Jones
2014-07-22 7:23 ` Kishon Vijay Abraham I
2014-07-22 7:28 ` [STLinux Kernel] " Maxime Coquelin
2014-07-23 7:58 ` Maxime Coquelin
2014-07-23 8:24 ` Kishon Vijay Abraham I [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=53CF714D.5090503@ti.com \
--to=kishon@ti.com \
--cc=kernel@stlinux.com \
--cc=kishon@uda0393678 \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infrared.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.