From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: UNGLinuxDriver@microchip.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
jacob.e.keller@intel.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robert.marko@sartura.hr
Subject: Re: [PATCH net-next v4 0/9] net: lan969x: add RGMII support
Date: Thu, 2 Jan 2025 09:37:31 +0000 [thread overview]
Message-ID: <Z3ZeW_N5bZkRAQ_L@shell.armlinux.org.uk> (raw)
In-Reply-To: <20241218143354.eh6iinemupxncblj@DEN-DL-M70577>
On Wed, Dec 18, 2024 at 02:33:54PM +0000, Daniel Machon wrote:
> I would like to defer the pontential removal of sparx5_port_verify_speed()
> function to a separate series (see comments on patch 6/9). Any chance for a
> maintainer to give the OK for that? I would like to give this series another
> spin before net-next closes. No changes in next version - except adding TB and
> RB tags.
There's no need to respin just to pick up tags that have been given -
patchwork will pick those up automatically.
I'd rather not have the current patch 6 merged, because we've had cases
in the past where stuff has been merged with "we'll fix it later" but
later doesn't seem to happen. We especially take this approach with new
kernel internal API functions - we don't merge them without a user,
because we've had too many cases where the user never appears.
We're currently at -rc5, which means -rc6 this Sunday 5th, -rc7 likely
next Sunday 12th, and probably the merge window opening on the 19th.
I think there's enough time for sparx5_port_verify_speed() to be
dropped during that window.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2025-01-02 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 13:40 [PATCH net-next v4 0/9] net: lan969x: add RGMII support Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 1/9] net: sparx5: do some preparation work Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 2/9] net: sparx5: add function for RGMII port check Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 3/9] net: sparx5: use is_port_rgmii() throughout Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 4/9] net: sparx5: skip low-speed configuration when port is RGMII Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 5/9] net: sparx5: only return PCS for modes that require it Daniel Machon
2024-12-13 19:45 ` Russell King (Oracle)
2024-12-13 13:41 ` [PATCH net-next v4 6/9] net: sparx5: verify RGMII speeds Daniel Machon
2024-12-13 19:48 ` Russell King (Oracle)
2024-12-16 12:10 ` Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 7/9] net: lan969x: add RGMII registers Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 8/9] net: lan969x: add RGMII implementation Daniel Machon
2024-12-13 13:41 ` [PATCH net-next v4 9/9] dt-bindings: net: sparx5: document RGMII delays Daniel Machon
2024-12-17 15:18 ` Rob Herring (Arm)
2024-12-13 19:54 ` [PATCH net-next v4 0/9] net: lan969x: add RGMII support Robert Marko
2024-12-18 14:33 ` Daniel Machon
2025-01-02 9:37 ` Russell King (Oracle) [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=Z3ZeW_N5bZkRAQ_L@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=jacob.e.keller@intel.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.marko@sartura.hr \
--cc=robh@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).