netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
	davem@davemloft.net, andrew@lunn.ch, linux@armlinux.org.uk,
	michael.chan@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 RESUBMIT net-next] bnxt: convert EEE handling to use linkmode bitmaps
Date: Fri, 09 Feb 2024 03:11:08 +0000	[thread overview]
Message-ID: <170744826824.23533.9844442167901588598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9123bf18-a0d0-404e-a7c4-d6c466b4c5e8@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 7 Feb 2024 17:47:35 +0100 you wrote:
> Convert EEE handling to use linkmode bitmaps. This prepares for removing
> the legacy bitmaps from struct ethtool_keee. No functional change
> intended. When replacing _bnxt_fw_to_ethtool_adv_spds() with
> _bnxt_fw_to_linkmode(), remove the fw_pause argument because it's
> always passed as 0.
> 
> Note:
> There's a discussion on whether the underlying implementation is correct,
> but it's independent of this mechanical conversion w/o functional change.
> 
> [...]

Here is the summary with links:
  - [v2,RESUBMIT,net-next] bnxt: convert EEE handling to use linkmode bitmaps
    https://git.kernel.org/netdev/net-next/c/6fb5dfee274c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-09  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 16:47 [PATCH v2 RESUBMIT net-next] bnxt: convert EEE handling to use linkmode bitmaps Heiner Kallweit
2024-02-07 18:07 ` Michael Chan
2024-02-09  3:11 ` patchwork-bot+netdevbpf [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=170744826824.23533.9844442167901588598.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.chan@broadcom.com \
    --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).