From: kernel test robot <lkp@intel.com>
To: Brian Silverman <brian.silverman@bluerivertech.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] can: m_can: Add driver for M_CAN hardware in NVIDIA devices
Date: Thu, 6 Jan 2022 14:06:17 +0800 [thread overview]
Message-ID: <202201061251.9fCLutdh-lkp@intel.com> (raw)
In-Reply-To: <20220106002514.24589-1-brian.silverman@bluerivertech.com>
Hi Brian,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on mkl-can-next/testing]
[also build test ERROR on v5.16-rc8 next-20220105]
[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/Brian-Silverman/can-m_can-Add-driver-for-M_CAN-hardware-in-NVIDIA-devices/20220106-082838
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git testing
config: i386-randconfig-a012-20220105
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project ca7ffe09dc6e525109e3cd570cc5182ce568be13)
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/3c5bcd8d6834eb3e2ac215c9aa35b662aca84aac
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Brian-Silverman/can-m_can-Add-driver-for-M_CAN-hardware-in-NVIDIA-devices/20220106-082838
git checkout 3c5bcd8d6834eb3e2ac215c9aa35b662aca84aac
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=i386 randconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=i386
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/net/can/m_can/Kconfig:29: syntax error
drivers/net/can/m_can/Kconfig:28: unknown statement "---help---"
drivers/net/can/m_can/Kconfig:29:warning: ignoring unsupported character ','
drivers/net/can/m_can/Kconfig:29: unknown statement "Say"
drivers/net/can/m_can/Kconfig:30:warning: ignoring unsupported character '.'
drivers/net/can/m_can/Kconfig:30: unknown statement "with"
drivers/net/can/m_can/Kconfig:31:warning: ignoring unsupported character '/'
drivers/net/can/m_can/Kconfig:31: unknown statement "This"
drivers/net/can/m_can/Kconfig:32: unknown statement "controller"
drivers/net/can/m_can/Kconfig:33:warning: ignoring unsupported character '.'
drivers/net/can/m_can/Kconfig:33: unknown statement "processor"
make[2]: *** [scripts/kconfig/Makefile:77: oldconfig] Error 1
make[1]: *** [Makefile:619: oldconfig] Error 2
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'oldconfig' not remade because of errors.
--
>> drivers/net/can/m_can/Kconfig:29: syntax error
drivers/net/can/m_can/Kconfig:28: unknown statement "---help---"
drivers/net/can/m_can/Kconfig:29:warning: ignoring unsupported character ','
drivers/net/can/m_can/Kconfig:29: unknown statement "Say"
drivers/net/can/m_can/Kconfig:30:warning: ignoring unsupported character '.'
drivers/net/can/m_can/Kconfig:30: unknown statement "with"
drivers/net/can/m_can/Kconfig:31:warning: ignoring unsupported character '/'
drivers/net/can/m_can/Kconfig:31: unknown statement "This"
drivers/net/can/m_can/Kconfig:32: unknown statement "controller"
drivers/net/can/m_can/Kconfig:33:warning: ignoring unsupported character '.'
drivers/net/can/m_can/Kconfig:33: unknown statement "processor"
make[2]: *** [scripts/kconfig/Makefile:77: olddefconfig] Error 1
make[1]: *** [Makefile:619: olddefconfig] Error 2
make: *** [Makefile:219: __sub-make] Error 2
make: Target 'olddefconfig' not remade because of errors.
vim +29 drivers/net/can/m_can/Kconfig
9
10 config CAN_M_CAN_PCI
11 tristate "Generic PCI Bus based M_CAN driver"
12 depends on PCI
13 help
14 Say Y here if you want to support Bosch M_CAN controller connected
15 to the pci bus.
16
17 config CAN_M_CAN_PLATFORM
18 tristate "Bosch M_CAN support for io-mapped devices"
19 depends on HAS_IOMEM
20 help
21 Say Y here if you want support for IO Mapped Bosch M_CAN controller.
22 This support is for devices that have the Bosch M_CAN controller
23 IP embedded into the device and the IP is IO Mapped to the processor.
24
25 config CAN_M_CAN_TEGRA
26 tristate "Bosch M_CAN support for io-mapped devices on NVIDIA Tegra"
27 depends on HAS_IOMEM
28 ---help---
> 29 Say Y here if you want support for IO Mapped Bosch M_CAN controller,
30 with additional NVIDIA Tegra-specific glue logic.
31 This support is for Tegra devices that have the Bosch M_CAN/M_TTCAN
32 controller IP embedded into the device and the IP is IO Mapped to the
33 processor.
34
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
parent reply other threads:[~2022-01-06 6:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220106002514.24589-1-brian.silverman@bluerivertech.com>]
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=202201061251.9fCLutdh-lkp@intel.com \
--to=lkp@intel.com \
--cc=brian.silverman@bluerivertech.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).