From: kernel test robot <lkp@intel.com>
To: Mateusz Holenko <mholenko@antmicro.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
devicetree@vger.kernel.org, linux-serial@vger.kernel.org
Cc: kbuild-all@lists.01.org, Stafford Horne <shorne@gmail.com>,
Karol Gugala <kgugala@antmicro.com>,
Mateusz Holenko <mholenko@antmicro.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v8 5/5] drivers/tty/serial: add LiteUART driver
Date: Thu, 16 Jul 2020 09:33:41 +0800 [thread overview]
Message-ID: <202007160958.EnoJdzni%lkp@intel.com> (raw)
In-Reply-To: <20200715130641.1953227-5-mholenko@antmicro.com>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi Mateusz,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on tty/tty-testing driver-core/driver-core-testing staging/staging-testing usb/usb-testing linus/master v5.8-rc5 next-20200715]
[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/Mateusz-Holenko/LiteX-SoC-controller-and-LiteUART-serial-driver/20200715-191229
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.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
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "litex_get_reg" [drivers/tty/serial/liteuart.ko] undefined!
>> ERROR: modpost: "litex_set_reg" [drivers/tty/serial/liteuart.ko] undefined!
---
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: 57268 bytes --]
prev parent reply other threads:[~2020-07-16 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 11:06 [PATCH v8 0/5] LiteX SoC controller and LiteUART serial driver Mateusz Holenko
2020-07-15 11:07 ` [PATCH v8 1/5] dt-bindings: vendor: add vendor prefix for LiteX Mateusz Holenko
2020-07-15 11:07 ` [PATCH v8 2/5] dt-bindings: soc: document LiteX SoC Controller bindings Mateusz Holenko
2020-07-15 17:54 ` Rob Herring
2020-07-15 11:07 ` [PATCH v8 3/5] drivers/soc/litex: add LiteX SoC Controller driver Mateusz Holenko
2020-07-15 11:07 ` [PATCH v8 4/5] dt-bindings: serial: document LiteUART bindings Mateusz Holenko
2020-07-15 11:08 ` [PATCH v8 5/5] drivers/tty/serial: add LiteUART driver Mateusz Holenko
2020-07-16 1:33 ` 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=202007160958.EnoJdzni%lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=kgugala@antmicro.com \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mholenko@antmicro.com \
--cc=robh+dt@kernel.org \
--cc=shorne@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox