From: kernel test robot <lkp@intel.com>
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Huacai Chen <chenhuacai@kernel.org>
Subject: [chenhuacai-loongson:loongarch-next 4/9] drivers/net/ethernet/netronome/nfp/bpf/jit.c:584:13: error: conflicting types for 'emit_nop'; have 'void(struct nfp_prog *)'
Date: Sat, 22 Mar 2025 22:24:02 +0800 [thread overview]
Message-ID: <202503222206.sC7OSxgr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git loongarch-next
head: 4448c4c96a8ab79f1bf9752abe2e25d7a56d9346
commit: c1a35b085d594b02302fb42dc95a9b606986323c [4/9] LoongArch: BPF: Fix off-by-one error in build_prologue()
config: loongarch-randconfig-001-20250322 (https://download.01.org/0day-ci/archive/20250322/202503222206.sC7OSxgr-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250322/202503222206.sC7OSxgr-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/202503222206.sC7OSxgr-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/netronome/nfp/bpf/jit.c:584:13: error: conflicting types for 'emit_nop'; have 'void(struct nfp_prog *)'
584 | static void emit_nop(struct nfp_prog *nfp_prog)
| ^~~~~~~~
In file included from arch/loongarch/include/asm/module.h:8,
from include/linux/module.h:33,
from include/linux/bpf.h:20,
from drivers/net/ethernet/netronome/nfp/bpf/jit.c:7:
arch/loongarch/include/asm/inst.h:525:20: note: previous definition of 'emit_nop' with type 'void(union loongarch_instruction *)'
525 | static inline void emit_nop(union loongarch_instruction *insn)
| ^~~~~~~~
vim +584 drivers/net/ethernet/netronome/nfp/bpf/jit.c
df4a37d8b53f9f Jakub Kicinski 2018-03-28 583
1c03e03f9b5278 Jakub Kicinski 2017-10-08 @584 static void emit_nop(struct nfp_prog *nfp_prog)
1c03e03f9b5278 Jakub Kicinski 2017-10-08 585 {
1c03e03f9b5278 Jakub Kicinski 2017-10-08 586 __emit_immed(nfp_prog, UR_REG_IMM, UR_REG_IMM, 0, 0, 0, 0, 0, 0, 0);
1c03e03f9b5278 Jakub Kicinski 2017-10-08 587 }
1c03e03f9b5278 Jakub Kicinski 2017-10-08 588
:::::: The code at line 584 was first introduced by commit
:::::: 1c03e03f9b5278701d4a0e3444b2de3b9ddc244b nfp: bpf: pad code with valid nops
:::::: TO: Jakub Kicinski <jakub.kicinski@netronome.com>
:::::: CC: David S. Miller <davem@davemloft.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-22 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202503222206.sC7OSxgr-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@kernel.org \
--cc=hengqi.chen@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.