Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Heiko Stuebner <heiko@sntech.de>,
	bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH net-next] net: phy: switch drivers to use dynamic feature detection
Date: Mon, 8 Apr 2019 20:45:45 +0200	[thread overview]
Message-ID: <3bc293a8-5966-fb40-e0b1-636f3a3dfe77@gmail.com> (raw)
In-Reply-To: <20190408181249.GH15267@lunn.ch>

On 08.04.2019 20:12, Andrew Lunn wrote:
>> Splitting the series and waiting for a Tested-by, as proposed by Richard,
>> may be problematic because most PHY drivers don't have a dedicated
>> maintainer, and we lack the hardware to test.
> 
> Well, we could split out those we know are likely to get tested.  I
> have a number of boards with Marvell devices i can test. Florian has
> Broadcom boards. I also have a couple of boards with Micrel KSZ8041,
> which would be interesting because they are Fast Ethernet. Bootlin can
> test some of the mscc PHYs.
> 
Great. Could you also test based on the series and the provide a
Tested-by for the PHY's which have been tested? Even if I split out
let's say the Marvell PHY driver, most likely just few of all the
supported Marvell PHY's can be tested.

> We also might want to get some targeted testing. The microchip_t1.c
> could be interesting, since it is a T1 device. There was another T1
> added in the last year, but i forget which.
> 
The T1 PHY driver isn't included in this series. It uses another
feature constant: PHY_BASIC_T1_FEATURES

> Just doing this testing might give us an idea if we really should
> expect problems.
> 
Sure. I tested and applied this change to the Realtek PHY driver
already.

>       Andrew
> 
Heiner

  reply	other threads:[~2019-04-08 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07  9:57 [PATCH net-next] net: phy: switch drivers to use dynamic feature detection Heiner Kallweit
     [not found] ` <0cc96fab-e102-c0d1-ade0-90e3e06dc9f1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-07 20:31   ` Florian Fainelli
     [not found]     ` <53f5d96e-4594-7a32-792d-4837479da7f2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-07 20:48       ` Heiner Kallweit
2019-04-07 22:13 ` Andrew Lunn
2019-04-08 17:45   ` Heiner Kallweit
2019-04-08 18:12     ` Andrew Lunn
2019-04-08 18:45       ` Heiner Kallweit [this message]
2019-04-08  2:38 ` Richard Cochran
2019-04-09 20:59 ` David Miller
2019-04-10 19:31   ` Heiner Kallweit
2019-04-10 19:33     ` Florian Fainelli

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=3bc293a8-5966-fb40-e0b1-636f3a3dfe77@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=heiko@sntech.de \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    /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