From: kernel test robot <lkp@intel.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jon Mason <jdmason@kudzu.us>
Subject: [linux-next:master 3951/5720] drivers/pci/endpoint/functions/pci-epf-vntb.c:975:5: warning: no previous prototype for 'pci_read'
Date: Sat, 25 Jun 2022 17:36:32 +0800 [thread overview]
Message-ID: <202206251702.1fAwOKaW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2f9cb3d3bd73fc2225d66aa8fcffb632ed3eb235
commit: ff32fac00d97661c715ee47bbfd867cae1f3aaf8 [3951/5720] NTB: EPF: support NTB transfer between PCI RC and EP connection
config: ia64-randconfig-r006-20220625
compiler: ia64-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ff32fac00d97661c715ee47bbfd867cae1f3aaf8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout ff32fac00d97661c715ee47bbfd867cae1f3aaf8
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/pci/endpoint/functions/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from arch/ia64/include/asm/pgtable.h:153,
from include/linux/pgtable.h:6,
from arch/ia64/include/asm/uaccess.h:40,
from include/linux/uaccess.h:11,
from arch/ia64/include/asm/sections.h:11,
from include/linux/interrupt.h:21,
from include/linux/pci.h:38,
from include/linux/pci-epf.h:15,
from include/linux/pci-epc.h:12,
from drivers/pci/endpoint/functions/pci-epf-vntb.c:44:
arch/ia64/include/asm/mmu_context.h: In function 'reload_context':
arch/ia64/include/asm/mmu_context.h:127:48: warning: variable 'old_rr4' set but not used [-Wunused-but-set-variable]
127 | unsigned long rr0, rr1, rr2, rr3, rr4, old_rr4;
| ^~~~~~~
drivers/pci/endpoint/functions/pci-epf-vntb.c: At top level:
>> drivers/pci/endpoint/functions/pci-epf-vntb.c:975:5: warning: no previous prototype for 'pci_read' [-Wmissing-prototypes]
975 | int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *val)
| ^~~~~~~~
>> drivers/pci/endpoint/functions/pci-epf-vntb.c:984:5: warning: no previous prototype for 'pci_write' [-Wmissing-prototypes]
984 | int pci_write(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 val)
| ^~~~~~~~~
{standard input}: Assembler messages:
{standard input}:8744: Error: Register number out of range 0..3
{standard input}:8745: Error: Register number out of range 0..3
{standard input}:8745: Warning: Use of 'mov' violates WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 47
{standard input}:8745: Warning: Only the first path encountering the conflict is reported
{standard input}:8744: Warning: This is the location of the conflicting usage
{standard input}:8746: Error: Register number out of range 0..3
{standard input}:8746: Warning: Use of 'mov' violates WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 47
{standard input}:8746: Warning: Only the first path encountering the conflict is reported
{standard input}:8744: Warning: This is the location of the conflicting usage
{standard input}:8746: Warning: Use of 'mov' violates WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 47
{standard input}:8746: Warning: Only the first path encountering the conflict is reported
{standard input}:8745: Warning: This is the location of the conflicting usage
{standard input}:8750: Error: Register number out of range 0..3
vim +/pci_read +975 drivers/pci/endpoint/functions/pci-epf-vntb.c
974
> 975 int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *val)
976 {
977 if (devfn == 0) {
978 memcpy(val, ((uint8_t *)pci_space) + where, size);
979 return 0;
980 }
981 return -1;
982 }
983
> 984 int pci_write(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 val)
985 {
986 return 0;
987 }
988
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-25 9:37 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=202206251702.1fAwOKaW-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=jdmason@kudzu.us \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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.