From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] [Patch v3 0/5] keystone2: serdes: add seredes driver
Date: Fri, 17 Oct 2014 22:01:50 +0300 [thread overview]
Message-ID: <5441679E.5050609@ti.com> (raw)
In-Reply-To: <54416755.6010405@ti.com>
On 10/17/2014 10:00 PM, Ivan Khoronzhuk wrote:
> On 10/17/2014 08:38 PM, Ivan Khoronzhuk wrote:
>> This patch series adds serdes driver, taking out it from
>> keystone_net driver.
>>
>> v3..v1:
>> - just rebase.
>
> is based on "[U-boot] [Patch v2 0/5] keystone2: generalize
> keystone_net driver usage"
> https://www.mail-archive.com/u-boot at lists.denx.de/msg148032.html
>
Oh sorry, get a wrong link
http://u-boot.10912.n7.nabble.com/U-boot-Patch-v2-0-5-keystone2-generalize-keystone-net-driver-usage-td190624.html
--
Regards,
Ivan Khoronzhuk
prev parent reply other threads:[~2014-10-17 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 17:38 [U-Boot] [U-boot] [Patch v3 0/5] keystone2: serdes: add seredes driver Ivan Khoronzhuk
2014-10-17 17:38 ` [U-Boot] [U-boot] [Patch v3 1/5] soc: add soc specific drivers directory Ivan Khoronzhuk
2014-10-17 17:39 ` [U-Boot] [U-boot] [Patch v3 2/5] soc: keystone_serdes: create a separate SGMII SerDes driver Ivan Khoronzhuk
2014-10-17 17:39 ` [U-Boot] [U-boot] [Patch v3 3/5] soc: keystone_serdes: enhance to use cmu/comlane/lane specific configurations Ivan Khoronzhuk
2014-10-17 17:39 ` [U-Boot] [U-boot] [Patch v3 4/5] soc: keystone_serdes: generalize to be used by other sub systems Ivan Khoronzhuk
2014-10-17 17:39 ` [U-Boot] [U-boot] [Patch v3 5/5] soc: keystone_serdes: generalize configuration mechanism Ivan Khoronzhuk
2014-10-17 19:00 ` [U-Boot] [U-boot] [Patch v3 0/5] keystone2: serdes: add seredes driver Ivan Khoronzhuk
2014-10-17 19:01 ` Ivan Khoronzhuk [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=5441679E.5050609@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=u-boot@lists.denx.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