From: Jakub Kicinski <kuba@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Daniel Golle <daniel@makrotopia.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] net: phy: realtek: fix status when link is down
Date: Wed, 15 Jan 2025 10:06:40 -0800 [thread overview]
Message-ID: <20250115100640.57e4132e@kernel.org> (raw)
In-Reply-To: <2e76c69d-a260-4067-a054-6a5d6cd18869@gmail.com>
On Wed, 15 Jan 2025 18:19:44 +0100 Heiner Kallweit wrote:
> Note that the Realtek PHY driver has just been moved to its own subdirectory.
> So you have to rebase your patch set.
Maybe not just yet. This is for net, and the rename was in net-next.
But as you may be alluding to 6.13 is likely to get released this
weekend, so the distinction will stop being relevant.
Let's keep rebasing on net for now, without anticipating the merge.
nit: subject should have said v2
next prev parent reply other threads:[~2025-01-15 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 14:43 [PATCH net 0/3] net: phy: realtek: fix status when link is down Daniel Golle
2025-01-15 14:43 ` [PATCH net 1/3] net: phy: realtek: clear 1000Base-T lpa if " Daniel Golle
2025-01-16 14:00 ` Michal Swiatkowski
2025-01-15 14:43 ` [PATCH net 2/3] net: phy: realtek: clear master_slave_state " Daniel Golle
2025-01-16 14:05 ` Michal Swiatkowski
2025-01-15 14:45 ` [PATCH net 3/3] net: phy: realtek: always clear NBase-T lpa Daniel Golle
2025-01-16 14:06 ` Michal Swiatkowski
2025-01-15 17:19 ` [PATCH net 0/3] net: phy: realtek: fix status when link is down Heiner Kallweit
2025-01-15 18:06 ` Jakub Kicinski [this message]
2025-01-17 12:10 ` patchwork-bot+netdevbpf
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=20250115100640.57e4132e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).