From: patchwork-bot+netdevbpf@kernel.org
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, sgoutham@marvell.com,
gakula@marvell.com, jerinj@marvell.com, lcherian@marvell.com,
sbhatta@marvell.com, naveenm@marvell.com, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [net-next] Octeontx2-af: Fix an issue in firmware shared data reserved space
Date: Mon, 04 Mar 2024 10:20:44 +0000 [thread overview]
Message-ID: <170954764481.3200.8588355582535112124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301110314.29800-1-hkelam@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 1 Mar 2024 16:33:14 +0530 you wrote:
> The last patch which added support to extend the firmware shared
> data to add channel data information has introduced a bug due to
> the reserved space not adjusted accordingly.
>
> This patch fixes the issue and also adds BUILD_BUG to avoid this
> regression error.
>
> [...]
Here is the summary with links:
- [net-next] Octeontx2-af: Fix an issue in firmware shared data reserved space
https://git.kernel.org/netdev/net-next/c/b8b85d048936
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-03-04 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:03 [net-next] Octeontx2-af: Fix an issue in firmware shared data reserved space Hariprasad Kelam
2024-03-04 10:20 ` 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=170954764481.3200.8588355582535112124.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.