From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Guenter Roeck <linux@roeck-us.net>,
Jiri Slaby <jirislaby@kernel.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v1 1/1] watchdog: wdt_pci: Correct the PCI ID vendor name
Date: Wed, 6 Oct 2021 04:47:14 +0800 [thread overview]
Message-ID: <202110060458.WLJ872sL-lkp@intel.com> (raw)
In-Reply-To: <20211005151445.89620-1-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 11367 bytes --]
Hi Andy,
I love your patch! Yet something to improve:
[auto build test ERROR on groeck-staging/hwmon-next]
[also build test ERROR on helgaas-pci/next linux/master linus/master v5.15-rc3 next-20210921]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Andy-Shevchenko/watchdog-wdt_pci-Correct-the-PCI-ID-vendor-name/20211005-231553
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
config: i386-randconfig-a001-20211004 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c0039de2953d15815448b4b3c3bafb45607781e0)
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://github.com/0day-ci/linux/commit/2ee39529d02438ed2b87a6a1cc2040b7d96563e1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Andy-Shevchenko/watchdog-wdt_pci-Correct-the-PCI-ID-vendor-name/20211005-231553
git checkout 2ee39529d02438ed2b87a6a1cc2040b7d96563e1
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/tty/serial/8250/8250_exar.c:825:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_2S, acces_com_2x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:154:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:826:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_4S, acces_com_4x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:158:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:827:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_8S, acces_com_8x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:162:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:828:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM232_8, acces_com_8x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:166:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:829:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_2SM, acces_com_2x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:170:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:830:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_4SM, acces_com_4x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:174:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
drivers/tty/serial/8250/8250_exar.c:831:2: error: use of undeclared identifier 'PCI_VENDOR_ID_ACCESSIO'
EXAR_DEVICE(ACCESSIO, COM_8SM, acces_com_8x),
^
drivers/tty/serial/8250/8250_exar.c:813:40: note: expanded from macro 'EXAR_DEVICE'
#define EXAR_DEVICE(vend, devid, bd) { PCI_DEVICE_DATA(vend, devid, &bd) }
^
include/linux/pci.h:1000:12: note: expanded from macro 'PCI_DEVICE_DATA'
.vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
^
<scratch space>:178:1: note: expanded from here
PCI_VENDOR_ID_ACCESSIO
^
7 errors generated.
vim +/PCI_VENDOR_ID_ACCESSIO +825 drivers/tty/serial/8250/8250_exar.c
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 814
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 815 #define IBM_DEVICE(devid, sdevid, bd) { \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 816 PCI_DEVICE_SUB( \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 817 PCI_VENDOR_ID_EXAR, \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 818 PCI_DEVICE_ID_EXAR_##devid, \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 819 PCI_VENDOR_ID_IBM, \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 820 PCI_SUBDEVICE_ID_IBM_##sdevid), 0, 0, \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 821 (kernel_ulong_t)&bd \
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 822 }
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 823
3637c46032515f Arvind Yadav 2017-07-23 824 static const struct pci_device_id exar_pci_tbl[] = {
24637007394e85 Andy Shevchenko 2020-05-12 @825 EXAR_DEVICE(ACCESSIO, COM_2S, acces_com_2x),
24637007394e85 Andy Shevchenko 2020-05-12 826 EXAR_DEVICE(ACCESSIO, COM_4S, acces_com_4x),
24637007394e85 Andy Shevchenko 2020-05-12 827 EXAR_DEVICE(ACCESSIO, COM_8S, acces_com_8x),
24637007394e85 Andy Shevchenko 2020-05-12 828 EXAR_DEVICE(ACCESSIO, COM232_8, acces_com_8x),
24637007394e85 Andy Shevchenko 2020-05-12 829 EXAR_DEVICE(ACCESSIO, COM_2SM, acces_com_2x),
24637007394e85 Andy Shevchenko 2020-05-12 830 EXAR_DEVICE(ACCESSIO, COM_4SM, acces_com_4x),
24637007394e85 Andy Shevchenko 2020-05-12 831 EXAR_DEVICE(ACCESSIO, COM_8SM, acces_com_8x),
10c5ccc3c6d32f Jay Dolan 2020-03-05 832
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 833 CONNECT_DEVICE(XR17C152, UART_2_232, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 834 CONNECT_DEVICE(XR17C154, UART_4_232, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 835 CONNECT_DEVICE(XR17C158, UART_8_232, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 836 CONNECT_DEVICE(XR17C152, UART_1_1, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 837 CONNECT_DEVICE(XR17C154, UART_2_2, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 838 CONNECT_DEVICE(XR17C158, UART_4_4, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 839 CONNECT_DEVICE(XR17C152, UART_2, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 840 CONNECT_DEVICE(XR17C154, UART_4, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 841 CONNECT_DEVICE(XR17C158, UART_8, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 842 CONNECT_DEVICE(XR17C152, UART_2_485, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 843 CONNECT_DEVICE(XR17C154, UART_4_485, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 844 CONNECT_DEVICE(XR17C158, UART_8_485, pbn_connect),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 845
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 846 IBM_DEVICE(XR17C152, SATURN_SERIAL_ONE_PORT, pbn_exar_ibm_saturn),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 847
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 848 /* Exar Corp. XR17C15[248] Dual/Quad/Octal UART */
24637007394e85 Andy Shevchenko 2020-05-12 849 EXAR_DEVICE(EXAR, XR17C152, pbn_exar_XR17C15x),
24637007394e85 Andy Shevchenko 2020-05-12 850 EXAR_DEVICE(EXAR, XR17C154, pbn_exar_XR17C15x),
24637007394e85 Andy Shevchenko 2020-05-12 851 EXAR_DEVICE(EXAR, XR17C158, pbn_exar_XR17C15x),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 852
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 853 /* Exar Corp. XR17V[48]35[248] Dual/Quad/Octal/Hexa PCIe UARTs */
24637007394e85 Andy Shevchenko 2020-05-12 854 EXAR_DEVICE(EXAR, XR17V352, pbn_exar_XR17V35x),
24637007394e85 Andy Shevchenko 2020-05-12 855 EXAR_DEVICE(EXAR, XR17V354, pbn_exar_XR17V35x),
24637007394e85 Andy Shevchenko 2020-05-12 856 EXAR_DEVICE(EXAR, XR17V358, pbn_exar_XR17V35x),
24637007394e85 Andy Shevchenko 2020-05-12 857 EXAR_DEVICE(EXAR, XR17V4358, pbn_exar_XR17V4358),
24637007394e85 Andy Shevchenko 2020-05-12 858 EXAR_DEVICE(EXAR, XR17V8358, pbn_exar_XR17V8358),
c6b9e95dde7b54 Valmer Huhn 2020-08-13 859 EXAR_DEVICE(COMMTECH, 4222PCIE, pbn_fastcom35x_2),
c6b9e95dde7b54 Valmer Huhn 2020-08-13 860 EXAR_DEVICE(COMMTECH, 4224PCIE, pbn_fastcom35x_4),
c6b9e95dde7b54 Valmer Huhn 2020-08-13 861 EXAR_DEVICE(COMMTECH, 4228PCIE, pbn_fastcom35x_8),
24637007394e85 Andy Shevchenko 2020-05-12 862
24637007394e85 Andy Shevchenko 2020-05-12 863 EXAR_DEVICE(COMMTECH, 4222PCI335, pbn_fastcom335_2),
24637007394e85 Andy Shevchenko 2020-05-12 864 EXAR_DEVICE(COMMTECH, 4224PCI335, pbn_fastcom335_4),
24637007394e85 Andy Shevchenko 2020-05-12 865 EXAR_DEVICE(COMMTECH, 2324PCI335, pbn_fastcom335_4),
24637007394e85 Andy Shevchenko 2020-05-12 866 EXAR_DEVICE(COMMTECH, 2328PCI335, pbn_fastcom335_8),
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 867 { 0, }
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 868 };
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 869 MODULE_DEVICE_TABLE(pci, exar_pci_tbl);
d0aeaa83f0b0f7 Sudip Mukherjee 2017-01-30 870
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38678 bytes --]
prev parent reply other threads:[~2021-10-05 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:14 Andy Shevchenko
2021-10-05 15:17 ` Andy Shevchenko
2021-10-05 15:52 ` Andy Shevchenko
2021-10-05 19:15 ` kernel test robot
2021-10-05 20:47 ` 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=202110060458.WLJ872sL-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=jirislaby@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=wim@linux-watchdog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®