All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Do not force master mode on unaffected PHY's
Date: Mon, 14 Nov 2016 12:26:05 +0100	[thread overview]
Message-ID: <b9479d92-487b-4992-de1a-6690b5be7580@redhat.com> (raw)
In-Reply-To: <20161108163859.14760-1-oliver@schinagl.nl>

Hi,

On 08-11-16 17:38, Olliver Schinagl wrote:
> The current implementation to force the PHY into master mode is to have a
> define which affects all realtek PHY's. This is not needed as the problem
> only exists in the RTL8211C chips. Let us thus turn this into a quirk flag
> instead.

Series looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans

  parent reply	other threads:[~2016-11-14 11:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 16:38 [U-Boot] [PATCH] Do not force master mode on unaffected PHY's Olliver Schinagl
2016-11-08 16:38 ` [U-Boot] [PATCH 1/3] net: phy: realtek: Use the BIT() macro Olliver Schinagl
2016-11-09 21:42   ` [U-Boot] [linux-sunxi] " Priit Laes
2016-11-09 22:40     ` Olliver Schinagl
2016-11-15  3:19   ` [U-Boot] " Joe Hershberger
2016-12-08 17:20   ` [U-Boot] " Joe Hershberger
2016-11-08 16:38 ` [U-Boot] [PATCH 2/3] net: phy: realtek: make define more concistent Olliver Schinagl
2016-11-08 23:17   ` [U-Boot] [linux-sunxi] " Emilio López
2016-11-09 10:34     ` Olliver Schinagl
2016-11-15  2:52   ` [U-Boot] " Joe Hershberger
2016-12-08 17:20   ` [U-Boot] net: phy: realtek: make define more consistent Joe Hershberger
2016-11-08 16:38 ` [U-Boot] [PATCH 3/3] net: phy: realtek: Only force master mode on rtl8211b/c Olliver Schinagl
2016-11-15  3:34   ` Joe Hershberger
2016-12-08 17:20   ` [U-Boot] " Joe Hershberger
2016-11-14 11:26 ` Hans de Goede [this message]
2016-11-14 14:11   ` [U-Boot] [PATCH] Do not force master mode on unaffected PHY's Olliver Schinagl
2016-11-14 14:13     ` Hans de Goede
2016-11-14 14:13       ` Olliver Schinagl

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=b9479d92-487b-4992-de1a-6690b5be7580@redhat.com \
    --to=hdegoede@redhat.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.