From: netdev-bot+sashiko@kernel.org
To: yijiangshan@kylinos.cn
Cc: sgoutham@marvell.com, rkannoth@marvell.com, gakula@marvell.com,
sbhatta@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
13667453960@163.com
Subject: Re: [PATCH net-next] octeontx2-af: consolidate RVU AFVF device id definitions
Date: Thu, 10 Sep 2026 09:42:10 +0000 [thread overview]
Message-ID: <178903333043.219967.16020637944756528838@kernel.org> (raw)
In-Reply-To: <20260908094051.666769-1-yijiangshan@kylinos.cn>
Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 1 · Low: 0
- [Medium] Incomplete consolidation: the patch's stated goal
("octeontx2-af: consolidate RVU AFVF device id definitions") is only…
--
octeontx2-af: consolidate RVU AFVF device id definitions
This moves the local PCI_DEVID_OCTEONTX2_RVU_AFVF define from af/rvu.c into
the "PCI device IDs" block in af/rvu.h, and renames RVU_LBK_VF_DEVID to the
same name so both users share one definition. The change is documented as
having no functional impact.
> diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu.h b/drivers/net/ethernet/marvell/octeontx2/af/rvu.h
> index 9afb7ac8969b5..fb4870cd18e9e 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu.h
> +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu.h
> @@ -22,6 +22,7 @@
>
> /* PCI device IDs */
> #define PCI_DEVID_OCTEONTX2_RVU_AF 0xA065
> +#define PCI_DEVID_OCTEONTX2_RVU_AFVF 0xA0F8
> #define PCI_DEVID_OCTEONTX2_LBK 0xA061
[Severity: Medium]
Is the consolidation complete here? There is still a third definition of
the same macro in nic/otx2_common.h:
drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h:
#include <rvu.h>
...
#define PCI_DEVID_OCTEONTX2_RVU_AFVF 0xA0F8
Since nic/Makefile adds:
ccflags-y += -I$(srctree)/drivers/net/ethernet/marvell/octeontx2/af
the <rvu.h> included by nic/otx2_common.h is the header modified by this
patch, so after this change every object built from nic/ (otx2_pf.o,
otx2_common.o, otx2_vf.o, rep.o) sees PCI_DEVID_OCTEONTX2_RVU_AFVF defined
twice within one translation unit.
Both replacement lists are the identical token 0xA0F8, so this is a benign
redefinition and no warning or build failure results. Would it make sense
to also drop the copy in nic/otx2_common.h, so that its users
(is_..._vf() in nic/otx2_common.h and the PCI id table in nic/otx2_vf.c)
pick up the definition through the included af/rvu.h?
As it stands, does the commit message claim more than the diff does when it
says the goal is to "consolidate RVU AFVF device id definitions" and
"drop the local define", given that two live definitions remain?
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260908094051.666769-1-yijiangshan%40kylinos.cn
prev parent reply other threads:[~2026-09-10 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:40 [PATCH net-next] octeontx2-af: consolidate RVU AFVF device id definitions Jiangshan Yi
2026-09-08 9:51 ` Ratheesh Kannoth
2026-09-08 10:31 ` Jiangshan Yi
2026-09-10 9:42 ` netdev-bot+sashiko [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=178903333043.219967.16020637944756528838@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=13667453960@163.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=yijiangshan@kylinos.cn \
/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