From: Simon Horman <horms@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, lcherian@marvell.com, jerinj@marvell.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net PATCH V4 0/3] Fix PFC related issues
Date: Fri, 25 Aug 2023 12:10:53 +0200 [thread overview]
Message-ID: <20230825100638.GL3523530@kernel.org> (raw)
In-Reply-To: <20230824081032.436432-1-sumang@marvell.com>
On Thu, Aug 24, 2023 at 01:40:29PM +0530, Suman Ghosh wrote:
> This patchset fixes multiple PFC related issues related to Octeon.
>
> Patch #1: octeontx2-pf: Fix PFC TX scheduler free
>
> Patch #2: octeontx2-af: CN10KB: fix PFC configuration
>
> Patch #3: octeonxt2-pf: Fix backpressure config for multiple PFC
> priorities to work simultaneously
>
> Hariprasad Kelam (1):
> octeontx2-af: CN10KB: fix PFC configuration
>
> Suman Ghosh (2):
> octeontx2-pf: Fix PFC TX scheduler free
> cteonxt2-pf: Fix backpressure config for multiple PFC priorities to
> work simultaneously
For series,
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-08-25 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:10 [net PATCH V4 0/3] Fix PFC related issues Suman Ghosh
2023-08-24 8:10 ` [net PATCH V4 1/3] octeontx2-pf: Fix PFC TX scheduler free Suman Ghosh
2023-08-24 8:10 ` [net PATCH V4 2/3] octeontx2-af: CN10KB: fix PFC configuration Suman Ghosh
2023-08-24 8:10 ` [net PATCH V4 3/3] cteonxt2-pf: Fix backpressure config for multiple PFC priorities to work simultaneously Suman Ghosh
2023-08-25 10:10 ` Simon Horman [this message]
2023-08-26 1:50 ` [net PATCH V4 0/3] Fix PFC related issues Jakub Kicinski
2023-08-26 2:27 ` [EXT] " Suman Ghosh
2023-08-26 2:00 ` patchwork-bot+netdevbpf
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=20230825100638.GL3523530@kernel.org \
--to=horms@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@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.