All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Walker <danielwa@cisco.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Andy Fleming <afleming@freescale.com>,
	Harini Katakam <harini.katakam@xilinx.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	HEMANT RAMDASI <hramdasi@cisco.com>,
	"Julius Hemanth Pitti -X (jpitti - MONTA VISTA SOFTWARE INC at
	Cisco)" <jpitti@cisco.com>
Subject: Re: Marvell phy errata origins?
Date: Tue, 9 May 2017 16:24:49 +0200	[thread overview]
Message-ID: <20170509142449.GA19251@lunn.ch> (raw)
In-Reply-To: <ffd12ac5-7501-0310-182f-1735c2da8165@cisco.com>

> According to Marvell this was errata for 88M1101 , and should not be
> applied to any other phy .. So we should be removing these lines and
> make a special aneg for 88M1101 then restore everything that doesn't
> need this back to the generic aneg,

Hi Daniel

Thanks for finding this out. Can you role a patch?

       Andrew

  reply	other threads:[~2017-05-09 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 13:16 Marvell phy errata origins? Daniel Walker
2017-04-18 14:04 ` Andrew Lunn
2017-04-18 14:18   ` Daniel Walker
2017-04-18 14:31     ` Harini Katakam
2017-04-18 14:35       ` Daniel Walker
2017-04-18 14:41         ` Harini Katakam
2017-04-18 14:56           ` Daniel Walker
2017-04-18 15:09             ` Harini Katakam
2017-05-09 13:58   ` Daniel Walker
2017-05-09 14:24     ` Andrew Lunn [this message]
2018-09-25 15:16   ` Daniel Walker
2018-09-25 15:34     ` Andrew Lunn
2018-09-25 15:39     ` Andrew Lunn
2018-09-25 17:30       ` Harini Katakam
2018-09-26  5:42         ` Harini Katakam
2018-09-26 15:35           ` Daniel Walker
2018-10-01 10:26             ` GokulChand Casheekar (gcasheek)
2018-10-04  7:27               ` GokulChand Casheekar (gcasheek)

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=20170509142449.GA19251@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=afleming@freescale.com \
    --cc=danielwa@cisco.com \
    --cc=f.fainelli@gmail.com \
    --cc=harini.katakam@xilinx.com \
    --cc=hramdasi@cisco.com \
    --cc=jpitti@cisco.com \
    --cc=netdev@vger.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 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.