From: patchwork-bot+netdevbpf@kernel.org
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ndabilpuram@marvell.com, sgoutham@marvell.com,
lcherian@marvell.com, gakula@marvell.com, jerinj@marvell.com,
hkelam@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [net-next PATCH] octeontx2-af: Sync NIX and NPA contexts from NDC to LLC/DRAM
Date: Mon, 01 Jul 2024 10:20:57 +0000 [thread overview]
Message-ID: <171982925733.8939.9678984506930226937.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1719592286-24699-1-git-send-email-sbhatta@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 28 Jun 2024 22:01:26 +0530 you wrote:
> From: Nithin Dabilpuram <ndabilpuram@marvell.com>
>
> Octeontx2 hardware uses Near Data Cache(NDC) block to cache
> contexts in it so that access to LLC/DRAM can be avoided.
> It is recommended in HRM to sync the NDC contents before
> releasing/resetting LF resources. Hence implement NDC_SYNC
> mailbox and sync contexts during driver teardown.
>
> [...]
Here is the summary with links:
- [net-next] octeontx2-af: Sync NIX and NPA contexts from NDC to LLC/DRAM
https://git.kernel.org/netdev/net-next/c/42c45ac1419c
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-07-01 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 16:31 [net-next PATCH] octeontx2-af: Sync NIX and NPA contexts from NDC to LLC/DRAM Subbaraya Sundeep
2024-07-01 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=171982925733.8939.9678984506930226937.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=ndabilpuram@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.