From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, yuehaibing@huawei.com,
horms@kernel.org, linux-kernel@vger.kernel.org, petrm@nvidia.com
Subject: Re: [PATCH net-next v5 0/2] ethtool: Add support for writing firmware
Date: Mon, 14 Oct 2024 02:40:47 +0000 [thread overview]
Message-ID: <172887364748.3904732.16162419800738341582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241009105347.2863905-1-danieller@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 9 Oct 2024 13:53:45 +0300 you wrote:
> In the CMIS specification for pluggable modules, LPL (Local Payload) and
> EPL (Extended Payload) are two types of data payloads used for managing
> various functions and features of the module.
>
> EPL payloads are used for more complex and extensive management functions
> that require a larger amount of data, so writing firmware blocks using EPL
> is much more efficient.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] net: ethtool: Add new parameters and a function to support EPL
https://git.kernel.org/netdev/net-next/c/edc344568922
- [net-next,v5,2/2] net: ethtool: Add support for writing firmware blocks using EPL payload
https://git.kernel.org/netdev/net-next/c/9a3b0d078bd8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-14 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 10:53 Danielle Ratson
2024-10-09 10:53 ` [PATCH net-next v5 1/2] net: ethtool: Add new parameters and a function to support EPL Danielle Ratson
2024-10-09 10:53 ` [PATCH net-next v5 2/2] net: ethtool: Add support for writing firmware blocks using EPL payload Danielle Ratson
2024-10-14 2:40 ` 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=172887364748.3904732.16162419800738341582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=yuehaibing@huawei.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
Powered by JetHome