From: kernel test robot <lkp@intel.com>
To: "andy.shevchenko" <andy.shevchenko@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [brgl:gpio/for-next 42/47] gpio-mmio.c:undefined reference to `iowrite64'
Date: Fri, 23 Feb 2024 20:44:00 +0800 [thread overview]
Message-ID: <202402232058.4eDf4GRs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
head: 7bb5f3a7ca8856c5c1fa26a6e3f58a1254019dc0
commit: 36e44186e0badfda499b65d4462c49783bf92314 [42/47] gpio: mmio: Support 64-bit BE access
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20240223/202402232058.4eDf4GRs-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240223/202402232058.4eDf4GRs-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/202402232058.4eDf4GRs-lkp@intel.com/
All errors (new ones prefixed by >>):
/usr/bin/ld: drivers/gpio/gpio-mmio.o: in function `bgpio_write64':
>> gpio-mmio.c:(.text+0x12e1): undefined reference to `iowrite64'
/usr/bin/ld: drivers/gpio/gpio-mmio.o: in function `bgpio_read64':
>> gpio-mmio.c:(.text+0x131d): undefined reference to `ioread64'
/usr/bin/ld: drivers/gpio/gpio-mmio.o: in function `bgpio_write64be':
>> gpio-mmio.c:(.text+0x1361): undefined reference to `iowrite64be'
/usr/bin/ld: drivers/gpio/gpio-mmio.o: in function `bgpio_read64be':
>> gpio-mmio.c:(.text+0x139d): undefined reference to `ioread64be'
collect2: error: ld returned 1 exit status
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-02-23 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:44 kernel test robot [this message]
2024-02-24 15:58 ` [brgl:gpio/for-next 42/47] gpio-mmio.c:undefined reference to `iowrite64' Linus Walleij
2024-02-24 18:56 ` Bartosz Golaszewski
2024-02-24 23:23 ` Andy Shevchenko
2024-02-25 21:09 ` Arnd Bergmann
2024-02-26 2:17 ` Andy Shevchenko
2024-02-26 6:35 ` Arnd Bergmann
2024-02-26 13:55 ` Bartosz Golaszewski
2024-02-26 15:33 ` Andy Shevchenko
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=202402232058.4eDf4GRs-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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.