linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Michael Klein <michael@fossekall.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	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: [net-next v4 1/3] net: phy: realtek: Clean up RTL8211E ExtPage access
Date: Mon, 24 Mar 2025 15:15:51 -0700	[thread overview]
Message-ID: <20250324151551.76869d80@kernel.org> (raw)
In-Reply-To: <20250317200532.93620-2-michael@fossekall.de>

Sorry for the delay, unfortunately this no longer applies:

Applying: net: phy: realtek: Clean up RTL8211E ExtPage access
error: patch failed: drivers/net/phy/realtek/realtek_main.c:28
error: drivers/net/phy/realtek/realtek_main.c: patch does not apply
Patch failed at 0001 net: phy: realtek: Clean up RTL8211E ExtPage access
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Given that some nits before you send v5 below..

On Mon, 17 Mar 2025 21:05:30 +0100 Michael Klein wrote:
> - Factor out RTL8211E extension page access code to
>   rtl8211e_modify_ext_page()/rtl8211e_read_ext_page() and add some
>   related #define:s
> - Group RTL8211E_* and RTL8211F_* #define:s
> - Clean up rtl8211e_config_init()

Sounds like this should be split into at least 2 patches.

>  static int rtl821x_probe(struct phy_device *phydev)
>  {
>  	struct device *dev = &phydev->mdio.dev;
> @@ -600,7 +617,8 @@ static int rtl8211f_led_hw_control_set(struct phy_device *phydev, u8 index,
>  
>  static int rtl8211e_config_init(struct phy_device *phydev)
>  {
> -	int ret = 0, oldpage;
> +	const u16 delay_mask = RTL8211E_CTRL_DELAY |
> +		RTL8211E_TX_DELAY | RTL8211E_RX_DELAY;

This would probably be easier to read if alinged.

	const u16 delay_mask = RTL8211E_CTRL_DELAY |
			       RTL8211E_TX_DELAY | 
			       RTL8211E_RX_DELAY;
-- 
pw-bot: cr

  reply	other threads:[~2025-03-24 22:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 20:05 [net-next v4 0/3] net: phy: realtek: Add support for PHY LEDs on Michael Klein
2025-03-17 20:05 ` [net-next v4 1/3] net: phy: realtek: Clean up RTL8211E ExtPage access Michael Klein
2025-03-24 22:15   ` Jakub Kicinski [this message]
2025-03-17 20:05 ` [net-next v4 2/3] net: phy: realtek: use __set_bit() in rtl8211f_led_hw_control_get() Michael Klein
2025-03-22 15:51   ` Andrew Lunn
2025-03-17 20:05 ` [net-next v4 3/3] net: phy: realtek: Add support for PHY LEDs on RTL8211E Michael Klein
2025-03-22 15:52   ` Andrew Lunn

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=20250324151551.76869d80@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@fossekall.de \
    --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).