From: Greg KH <gregkh@linuxfoundation.org>
To: "Minh Tiến Nguyễn" <zizuzacker@gmail.com>
Cc: stable@vger.kernel.org, Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org
Subject: Re: [PATCH 6.6.y] net: usb: lan78xx: program MAC_CR for LAN7801 fixed-PHY link
Date: Wed, 30 Sep 2026 16:01:29 +0200 [thread overview]
Message-ID: <2026093022-concerned-gestate-2a88@gregkh> (raw)
In-Reply-To: <CAH9t78zjHGm-EFmjeJy3fMZ0fs3m+ZKWynaJkd8GDZdWoZDLHw@mail.gmail.com>
On Tue, Sep 29, 2026 at 02:36:13PM +0700, Minh Tiến Nguyễn wrote:
> > Please backport exactly what is in the mainline tree, otherwise odds are,
> > this one-off fix will be found incorrect (we always get it wrong...)
>
> Hi Greg,
> Sorry for the long silence. In June the board was still in development
> and I only made the link work; I've only now had time to recheck this
> against mainline and test it on the hardware.
>
> You were right. Please drop my patch; these two mainline commits fix
> the same bug:
>
> 5160b129f65f ("lan78xx: Enable 125 MHz CLK configuration for LAN7801 if
> NO EEPROM is detected")
> 799f532de136 ("lan78xx: Enable Auto Speed and Auto Duplex configuration
> for LAN7801 if NO EEPROM is detected")
>
> Could you apply them, in that order, to the stable trees that don't
> have them yet (6.6.y and older)? They apply cleanly. I tested them with
> the 6.6.y and 6.1.y driver on the board: without them the LAN7801 MAC
> stays at 10 Mb/s and passes no traffic, with them the link runs at
> 1000/full with no errors.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2026-09-30 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 12:15 [PATCH 6.6.y] net: usb: lan78xx: program MAC_CR for LAN7801 fixed-PHY link Nguyen Minh Tien
2026-06-05 14:57 ` Greg KH
[not found] ` <CAH9t78zjHGm-EFmjeJy3fMZ0fs3m+ZKWynaJkd8GDZdWoZDLHw@mail.gmail.com>
2026-09-30 14:01 ` Greg KH [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=2026093022-concerned-gestate-2a88@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=woojung.huh@microchip.com \
--cc=zizuzacker@gmail.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 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.