From: kernel test robot <lkp@intel.com>
To: vmukunda <vmukunda@marvell.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Sunil Goutham <sgoutham@marvell.com>,
Ratheesh Kannoth <rkannoth@marvell.com>,
Geetha sowjanya <gakula@marvell.com>,
Subbaraya Sundeep <sbhatta@marvell.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
vmukunda <vmukunda@marvell.com>
Subject: Re: [PATCH net] octeontx2-af: Fix npc_delete_flow counter read for cn20k
Date: Sat, 24 Oct 2026 18:11:39 +0800 [thread overview]
Message-ID: <202610241814.S7V8CsQq-lkp@intel.com> (raw)
In-Reply-To: <20261023100112.3402726-1-vmukunda@marvell.com>
Hi vmukunda,
kernel test robot noticed the following build errors:
[auto build test ERROR on net/main]
url: https://github.com/intel-lab-lkp/linux/commits/vmukunda/octeontx2-af-Fix-npc_delete_flow-counter-read-for-cn20k/20261023-100112
base: net/main
patch link: https://lore.kernel.org/r/20261023100112.3402726-1-vmukunda%40marvell.com
patch subject: [PATCH net] octeontx2-af: Fix npc_delete_flow counter read for cn20k
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20261024/202610241814.S7V8CsQq-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261024/202610241814.S7V8CsQq-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610241814.S7V8CsQq-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/net/ethernet/marvell/octeontx2/af/rvu.h:13,
from drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:11:
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c: In function 'rvu_mbox_handler_npc_delete_flow':
>> drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:1962:58: error: 'rvu_pdev' undeclared (first use in this function)
1962 | if (blkaddr && !is_cn20k(rvu_pdev))
| ^~~~~~~~
include/linux/soc/marvell/silicons.h:22:41: note: in definition of macro 'is_cn20k'
22 | #define is_cn20k(pdev) ((void)(pdev), 0)
| ^~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:1962:58: note: each undeclared identifier is reported only once for each function it appears in
include/linux/soc/marvell/silicons.h:22:41: note: in definition of macro 'is_cn20k'
22 | #define is_cn20k(pdev) ((void)(pdev), 0)
| ^~~~
include/linux/soc/marvell/silicons.h:22:46: warning: left-hand operand of comma expression has no effect [-Wunused-value]
22 | #define is_cn20k(pdev) ((void)(pdev), 0)
| ^
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:1962:49: note: in expansion of macro 'is_cn20k'
1962 | if (blkaddr && !is_cn20k(rvu_pdev))
| ^~~~~~~~
vim +/rvu_pdev +1962 drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c
1932
1933 int rvu_mbox_handler_npc_delete_flow(struct rvu *rvu,
1934 struct npc_delete_flow_req *req,
1935 struct npc_delete_flow_rsp *rsp)
1936 {
1937 struct npc_mcam *mcam = &rvu->hw->mcam;
1938 struct rvu_npc_mcam_rule *iter, *tmp;
1939 u16 pcifunc = req->hdr.pcifunc;
1940 struct list_head del_list;
1941 int blkaddr;
1942
1943 req->entry = npc_cn20k_vidx2idx(req->entry);
1944 req->start = npc_cn20k_vidx2idx(req->start);
1945 req->end = npc_cn20k_vidx2idx(req->end);
1946
1947 INIT_LIST_HEAD(&del_list);
1948
1949 mutex_lock(&mcam->lock);
1950 list_for_each_entry_safe(iter, tmp, &mcam->mcam_rules, list) {
1951 if (iter->owner == pcifunc) {
1952 /* All rules */
1953 if (req->all) {
1954 list_move_tail(&iter->list, &del_list);
1955 /* Range of rules */
1956 } else if (req->end && iter->entry >= req->start &&
1957 iter->entry <= req->end) {
1958 list_move_tail(&iter->list, &del_list);
1959 /* single rule */
1960 } else if (req->entry == iter->entry) {
1961 blkaddr = rvu_get_blkaddr(rvu, BLKTYPE_NPC, 0);
> 1962 if (blkaddr && !is_cn20k(rvu_pdev))
1963 rsp->cntr_val = rvu_read64(rvu, blkaddr,
1964 NPC_AF_MATCH_STATX(iter->cntr));
1965 list_move_tail(&iter->list, &del_list);
1966 break;
1967 }
1968 }
1969 }
1970 mutex_unlock(&mcam->lock);
1971
1972 list_for_each_entry_safe(iter, tmp, &del_list, list) {
1973 u16 entry = iter->entry;
1974
1975 /* clear the mcam entry target pcifunc */
1976 mcam->entry2target_pffunc[entry] = 0x0;
1977 if (npc_delete_flow(rvu, iter, pcifunc))
1978 dev_err(rvu->dev, "rule deletion failed for entry:%u",
1979 entry);
1980 }
1981
1982 return 0;
1983 }
1984
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-10-24 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:01 [PATCH net] octeontx2-af: Fix npc_delete_flow counter read for cn20k vmukunda
2026-10-23 10:06 ` netdev-bot+sinfo
2026-10-24 0:03 ` kernel test robot
2026-10-24 0:58 ` kernel test robot
2026-10-24 10:11 ` kernel test robot [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=202610241814.S7V8CsQq-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=vmukunda@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.