All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Virdi <amit.virdi@st.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 3/8] net/designware: Phy address fix
Date: Thu, 5 Apr 2012 10:45:12 +0530	[thread overview]
Message-ID: <4F7D2A60.2080304@st.com> (raw)
In-Reply-To: <1332756599-19304-4-git-send-email-amit.virdi@st.com>

Hi Joe,

On 3/26/2012 3:39 PM, Amit VIRDI wrote:
> From: Vipin KUMAR<vipin.kumar@st.com>
>
> The code assumes the phy address to be>  0, which is not true, the phy address
> can be in the range 0-31.
>
> Signed-off-by: Vipin Kumar<vipin.kumar@st.com>
> Signed-off-by: Amit Virdi<amit.virdi@st.com>

Could you please confirm if you have applied this patch too?

Thanks n Best Regards
Amit Virdi

  reply	other threads:[~2012-04-05  5:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 10:09 [U-Boot] [PATCH V2 0/8] net/designware: Bug fixes Amit Virdi
2012-03-26 10:09 ` [U-Boot] [PATCH V2 1/8] net/designware: Fix to restore hw mac address Amit Virdi
2012-04-04 17:31   ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 2/8] net/designware: Fix the max frame length size Amit Virdi
2012-04-04 17:34   ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 3/8] net/designware: Phy address fix Amit Virdi
2012-04-05  5:15   ` Amit Virdi [this message]
2012-04-05 14:36     ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 4/8] net/designware: Consecutive writes must have delay Amit Virdi
2012-03-26 10:09 ` [U-Boot] [PATCH V2 5/8] net/designware: Try configuring phy on each dw_eth_init Amit Virdi
2012-04-04 17:35   ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 6/8] net/designware: Program phy registers when auto-negotiation is ON Amit Virdi
2012-04-04 17:35   ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 7/8] net/designware: Set ANAR to 0x1e1 Amit Virdi
2012-04-04 17:36   ` Joe Hershberger
2012-03-26 10:09 ` [U-Boot] [PATCH V2 8/8] net/designware: Change timeout loop implementation Amit Virdi
2012-04-04 17:36   ` Joe Hershberger

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=4F7D2A60.2080304@st.com \
    --to=amit.virdi@st.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.