linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, zyta@marvell.com, richardcochran@gmail.com,
	kuba@kernel.org, sbhatta@marvell.com, lcherian@marvell.com,
	sgoutham@marvell.com, jerinj@marvell.com
Subject: Re: [net PATCH] octeontx2-af: Fix PKIND overlap between LBK and LMAC interfaces
Date: Sun, 25 Jul 2021 08:30:05 +0000	[thread overview]
Message-ID: <162720180517.26018.16145315014171443488.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210725075824.6378-1-gakula@marvell.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Sun, 25 Jul 2021 13:28:24 +0530 you wrote:
> Currently PKINDs are not assigned to LBK channels.
> The default value of LBK_CHX_PKIND (channel to PKIND mapping) register
> is zero, which is resulting in a overlap of pkind between LBK and CGX
> LMACs. When KPU1 parser config is modified when PTP timestamping is
> enabled on the CGX LMAC interface it is impacting traffic on LBK
> interfaces as well.
> 
> [...]

Here is the summary with links:
  - [net] octeontx2-af: Fix PKIND overlap between LBK and LMAC interfaces
    https://git.kernel.org/netdev/net/c/ac059d16442f

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



      reply	other threads:[~2021-07-25  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25  7:58 [net PATCH] octeontx2-af: Fix PKIND overlap between LBK and LMAC interfaces Geetha sowjanya
2021-07-25  8:30 ` 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=162720180517.26018.16145315014171443488.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gakula@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=zyta@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 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).