From: Leon Romanovsky <leon@kernel.org>
To: Srujana Challa <schalla@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, jerinj@marvell.com,
sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
sbhatta@marvell.com, hkelam@marvell.com
Subject: Re: [PATCH v2 net-next,0/8] octeontx2-af: Miscellaneous changes for CPT
Date: Sun, 15 Jan 2023 10:54:15 +0200 [thread overview]
Message-ID: <Y8O/N0oHX4VtHMDO@unreal> (raw)
In-Reply-To: <20230111122343.928694-1-schalla@marvell.com>
On Wed, Jan 11, 2023 at 05:53:35PM +0530, Srujana Challa wrote:
> This patchset consists of miscellaneous changes for CPT.
> - Adds a new mailbox to reset the requested CPT LF.
> - Modify FLR sequence as per HW team suggested.
> - Adds support to recover CPT engines when they gets fault.
> - Updates CPT inbound inline IPsec configuration mailbox,
> as per new generation of the OcteonTX2 chips.
> - Adds a new mailbox to return CPT FLT Interrupt info.
>
> ---
> v2:
> - Addressed a review comment.
> v1:
> - Dropped patch "octeontx2-af: Fix interrupt name strings completely"
> to submit to net.
> ---
>
> Nithin Dabilpuram (1):
> octeontx2-af: restore rxc conf after teardown sequence
>
> Srujana Challa (7):
> octeontx2-af: recover CPT engine when it gets fault
> octeontx2-af: add mbox for CPT LF reset
> octeontx2-af: modify FLR sequence for CPT
> octeontx2-af: optimize cpt pf identification
> octeontx2-af: update CPT inbound inline IPsec config mailbox
> octeontx2-af: add ctx ilen to cpt lf alloc mailbox
> octeontx2-af: add mbox to return CPT_AF_FLT_INT info
>
Except not-so-great commit messages and huge amount of timeout
loops in patch #3, the series is ok.
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2023-01-15 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 12:23 [PATCH v2 net-next,0/8] octeontx2-af: Miscellaneous changes for CPT Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,1/8] octeontx2-af: recover CPT engine when it gets fault Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,2/8] octeontx2-af: add mbox for CPT LF reset Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,3/8] octeontx2-af: modify FLR sequence for CPT Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,4/8] octeontx2-af: optimize cpt pf identification Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,5/8] octeontx2-af: restore rxc conf after teardown sequence Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,/8] octeontx2-af: update CPT inbound inline IPsec config mailbox Srujana Challa
2023-01-16 10:30 ` patchwork-bot+netdevbpf
2023-01-11 12:23 ` [PATCH v2 net-next,7/8] octeontx2-af: add ctx ilen to cpt lf alloc mailbox Srujana Challa
2023-01-11 12:23 ` [PATCH v2 net-next,8/8] octeontx2-af: add mbox to return CPT_AF_FLT_INT info Srujana Challa
2023-01-15 8:54 ` Leon Romanovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-12 4:41 [PATCH v2 net-next,0/8] octeontx2-af: Miscellaneous changes for CPT Srujana Challa
2023-01-12 5:24 ` Jakub Kicinski
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=Y8O/N0oHX4VtHMDO@unreal \
--to=leon@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=schalla@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.