stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: mathieu.tortuyaux@gmail.com
Cc: stable@vger.kernel.org, Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Subject: Re: [PATCH 6.12.y 0/3] r8169: add support for RTL8125D
Date: Wed, 2 Jul 2025 12:04:39 +0200	[thread overview]
Message-ID: <2025070224-plethora-thread-8ef2@gregkh> (raw)
In-Reply-To: <20250630142717.70619-1-mathieu.tortuyaux@gmail.com>

On Mon, Jun 30, 2025 at 04:27:13PM +0200, mathieu.tortuyaux@gmail.com wrote:
> From: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
> 
> Hi,
> 
> This backports support for Realtek device 0x688 on Kernel 6.12.y:
> * Tested in Flatcar CI w/ Kernel 6.12.35 on qemu (for regression): https://github.com/flatcar/scripts/pull/3006
> * The user requesting this support has confirmed correct behavior: https://github.com/flatcar/Flatcar/issues/1749#issuecomment-3005483988 
> 
> The two other commits ("net: phy: realtek: merge the drivers for
> internal NBase-T PHY's" and "net: phy: realtek: add RTL8125D-internal PHY")
> are required to add support here as well, otherwise it fails with:
> ```
> $ dmesg
> ...
> r8169 ... : no dedicated PHY driver found for PHY ID 0x001cc841
> ...
> ```
> 
> Thanks and have a great day,
> 
> Mathieu (@tormath1)
> 
> Heiner Kallweit (3):
>   r8169: add support for RTL8125D
>   net: phy: realtek: merge the drivers for internal NBase-T PHY's
>   net: phy: realtek: add RTL8125D-internal PHY
> 
>  drivers/net/ethernet/realtek/r8169.h          |  1 +
>  drivers/net/ethernet/realtek/r8169_main.c     | 23 +++++---
>  .../net/ethernet/realtek/r8169_phy_config.c   | 10 ++++
>  drivers/net/phy/realtek.c                     | 54 +++++++++++++++----
>  4 files changed, 71 insertions(+), 17 deletions(-)

You did not sign off on any of these patches that you forwarded on :(

  parent reply	other threads:[~2025-07-02 10:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 14:27 [PATCH 6.12.y 0/3] r8169: add support for RTL8125D mathieu.tortuyaux
2025-06-30 14:27 ` [PATCH 6.12.y 1/3] " mathieu.tortuyaux
2025-07-01  1:15   ` Sasha Levin
2025-06-30 14:27 ` [PATCH 6.12.y 2/3] net: phy: realtek: merge the drivers for internal NBase-T PHY's mathieu.tortuyaux
2025-07-01  1:15   ` Sasha Levin
2025-06-30 14:27 ` [PATCH 6.12.y 3/3] net: phy: realtek: add RTL8125D-internal PHY mathieu.tortuyaux
2025-07-01  1:15   ` Sasha Levin
2025-07-02 10:04 ` Greg KH [this message]
2025-07-02 10:28   ` [PATCH 6.12.y v2 0/3] r8169: add support for RTL8125D mathieu.tortuyaux
2025-07-02 10:28     ` [PATCH 6.12.y v2 1/3] " mathieu.tortuyaux
2025-07-03 18:34       ` Sasha Levin
2025-07-02 10:28     ` [PATCH 6.12.y v2 2/3] net: phy: realtek: merge the drivers for internal NBase-T PHY's mathieu.tortuyaux
2025-07-03 18:34       ` Sasha Levin
2025-07-02 10:28     ` [PATCH 6.12.y v2 3/3] net: phy: realtek: add RTL8125D-internal PHY mathieu.tortuyaux
2025-07-03 18:35       ` Sasha Levin

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=2025070224-plethora-thread-8ef2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=mathieu.tortuyaux@gmail.com \
    --cc=mtortuyaux@microsoft.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).