From: Simon Horman <horms@kernel.org>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, sgoutham@marvell.com,
gakula@marvell.com, bbhushan2@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Linu Cherian <lcherian@marvell.com>
Subject: Re: [net-next PATCH 3/4] octeontx2-af: npa: cn20k: Add debugfs for Halo
Date: Wed, 18 Mar 2026 15:18:40 +0000 [thread overview]
Message-ID: <20260318151840.GD1753385@horms.kernel.org> (raw)
In-Reply-To: <1773665859-4036-4-git-send-email-sbhatta@marvell.com>
On Mon, Mar 16, 2026 at 06:27:38PM +0530, Subbaraya Sundeep wrote:
...
> diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c b/drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c
...
> @@ -1204,6 +1210,20 @@ static void print_npa_pool_ctx(struct seq_file *m, struct npa_aq_enq_rsp *rsp)
> seq_printf(m, "W8: fc_msh_dst\t\t%d\n", pool->fc_msh_dst);
> }
>
> +static inline char *npa_ctype_str(int ctype)
Please don't use the inline keyword in C code unless there is a
demonstrable - usually performance - reason to do so.
Also, I wonder if the return type for this function should be const.
> +{
> + switch (ctype) {
> + case NPA_AQ_CTYPE_AURA:
> + return "aura";
> + case NPA_AQ_CTYPE_HALO:
> + return "halo";
> + case NPA_AQ_CTYPE_POOL:
> + return "pool";
> + default:
> + return NULL;
> + }
> +}
> +
...
next prev parent reply other threads:[~2026-03-18 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 12:57 [net-next PATCH 0/4] octeontx2: CN20K NPA Halo context support Subbaraya Sundeep
2026-03-16 12:57 ` [net-next PATCH 1/4] octeontx2-af: npa: cn20k: Add NPA Halo support Subbaraya Sundeep
2026-03-18 15:21 ` [net-next,1/4] " Simon Horman
2026-03-16 12:57 ` [net-next PATCH 2/4] octeontx2-af: npa: cn20k: Add DPC support Subbaraya Sundeep
2026-03-18 15:20 ` [net-next,2/4] " Simon Horman
2026-03-16 12:57 ` [net-next PATCH 3/4] octeontx2-af: npa: cn20k: Add debugfs for Halo Subbaraya Sundeep
2026-03-18 15:18 ` Simon Horman [this message]
2026-03-16 12:57 ` [net-next PATCH 4/4] octeontx2-pf: cn20k: Use unified Halo context Subbaraya Sundeep
2026-03-18 15:06 ` [net-next,4/4] " Simon Horman
2026-03-18 15:12 ` [net-next PATCH 4/4] " Simon Horman
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=20260318151840.GD1753385@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@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 \
/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.