From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] [Patch v2 0/6] keystone2: add network support for K2E SoC and EVM
Date: Fri, 17 Oct 2014 22:10:57 +0300 [thread overview]
Message-ID: <544169C1.6080804@ti.com> (raw)
In-Reply-To: <1413568877-20146-1-git-send-email-ivan.khoronzhuk@ti.com>
On 10/17/2014 09:01 PM, Ivan Khoronzhuk wrote:
> These patches add network support for Keystne2 Edison SoC boards.
>
> Based on
> "[U-boot] [Patch v2 0/5] keystone_net: use MDIO bus and eth PHY frameworks"
> http://patchwork.ozlabs.org/patch/322289/
link update
https://www.mail-archive.com/u-boot at lists.denx.de/msg150350.html
--
Regards,
Ivan Khoronzhuk
prev parent reply other threads:[~2014-10-17 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 18:01 [U-Boot] [U-boot] [Patch v2 0/6] keystone2: add network support for K2E SoC and EVM Ivan Khoronzhuk
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 1/6] ARM: keystone2: keysonte_nav: add support for K2E SoC Ivan Khoronzhuk
2014-10-23 17:14 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 2/6] net: keystone_serdes: add keystone K2E SoC support Ivan Khoronzhuk
2014-10-23 17:14 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 3/6] net: keystone_net: add Keystone2 " Ivan Khoronzhuk
2014-10-23 17:14 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 4/6] net: keystone_net: increase PHY auto negotiate time Ivan Khoronzhuk
2014-10-23 17:14 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 5/6] ARM: keystone: clock: add support for K2E SoCs Ivan Khoronzhuk
2014-10-23 17:14 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 18:01 ` [U-Boot] [U-boot] [Patch v2 6/6] board: k2e_evm: add network support Ivan Khoronzhuk
2014-10-23 17:15 ` [U-Boot] [U-Boot, U-boot, v2, " Tom Rini
2014-10-17 19:10 ` 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=544169C1.6080804@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 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.