From: Heiner Kallweit <hkallweit1@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Subject: Re: [PATCH net-next] r8169: improve RTL8411b phy-down fixup
Date: Fri, 17 Nov 2023 07:43:04 +0100 [thread overview]
Message-ID: <2c3087b1-706e-4b8c-839c-1db1b99c5080@gmail.com> (raw)
In-Reply-To: <f1a5f918-e9fd-48e6-8956-2c79648e563e@gmail.com>
On 13.11.2023 20:13, Heiner Kallweit wrote:
> Mirsad proposed a patch to reduce the number of spinlock lock/unlock
> operations and the function code size. This can be further improved
> because the function sets a consecutive register block.
>
> Suggested-by: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/net/ethernet/realtek/r8169_main.c | 139 +++++-----------------
> 1 file changed, 28 insertions(+), 111 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/r8169_main.c b/drivers/net/ethernet/realtek/r8169_main.c
> index 93929d835..e883db468 100644
> --- a/drivers/net/ethernet/realtek/r8169_main.c
> +++ b/drivers/net/ethernet/realtek/r8169_main.c
> @@ -3084,6 +3084,33 @@ static void rtl_hw_start_8168g_2(struct rtl8169_private *tp)
> rtl_ephy_init(tp, e_info_8168g_2);
> }
>
Is there a specific reason why patch has status "Deferred" in patchwork?
next prev parent reply other threads:[~2023-11-17 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 19:13 [PATCH net-next] r8169: improve RTL8411b phy-down fixup Heiner Kallweit
2023-11-15 17:35 ` Simon Horman
2023-11-15 22:17 ` Mirsad Todorovac
2023-11-16 5:56 ` Mirsad Todorovac
2023-11-17 6:43 ` Heiner Kallweit [this message]
2023-11-18 18:24 ` Jakub Kicinski
2023-11-18 22:30 ` 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=2c3087b1-706e-4b8c-839c-1db1b99c5080@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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).