From: Tomas Melin <tomas.melin@vaisala.com>
To: kernel test robot <lkp@intel.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michal Simek <monstr@monstr.eu>
Cc: oe-kbuild-all@lists.linux.dev, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] rtc: zynqmp: rework read_offset
Date: Thu, 15 Jan 2026 09:41:51 +0200 [thread overview]
Message-ID: <fded3e4f-f292-48bf-aea7-0c8e71f7e056@vaisala.com> (raw)
In-Reply-To: <202601150836.Yk8DcSZW-lkp@intel.com>
Hi,
On 15/01/2026 02:42, kernel test robot wrote:
>
> arm-linux-gnueabi-ld: drivers/spi/spi-amlogic-spifc-a4.o: in function `aml_sfc_set_bus_width':
> spi-amlogic-spifc-a4.c:(.text.aml_sfc_set_bus_width+0x8c): undefined reference to `__ffsdi2'
> arm-linux-gnueabi-ld: spi-amlogic-spifc-a4.c:(.text.aml_sfc_set_bus_width+0xac): undefined reference to `__ffsdi2'
> arm-linux-gnueabi-ld: spi-amlogic-spifc-a4.c:(.text.aml_sfc_set_bus_width+0xcc): undefined reference to `__ffsdi2'
> arm-linux-gnueabi-ld: drivers/rtc/rtc-zynqmp.o: in function `xlnx_rtc_read_offset':
>>> rtc-zynqmp.c:(.text.xlnx_rtc_read_offset+0xd0): undefined reference to `__aeabi_ldivmod'
>>> arm-linux-gnueabi-ld: rtc-zynqmp.c:(.text.xlnx_rtc_read_offset+0x15c): undefined reference to `__aeabi_ldivmod'
AFAIU this is related to compiling for arm 32 bit target. Is this error
relevant since this driver is for aarch64 zynqmp specifically? If so,
what would be correct way of fixing?
Thanks,
Tomas
>
next prev parent reply other threads:[~2026-01-15 7:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 12:51 [PATCH v2 0/5] rtc: zynqmp: fixes for read and set offset Tomas Melin
2026-01-08 12:51 ` [PATCH v2 1/5] rtc: zynqmp: correct frequency value Tomas Melin
2026-01-14 15:35 ` T, Harini
2026-01-08 12:51 ` [PATCH v2 2/5] rtc: zynqmp: check calibration max value Tomas Melin
2026-01-14 15:35 ` T, Harini
2026-01-08 12:51 ` [PATCH v2 3/5] rtc: zynqmp: rework read_offset Tomas Melin
2026-01-14 15:36 ` T, Harini
2026-01-15 0:42 ` kernel test robot
2026-01-15 7:41 ` Tomas Melin [this message]
2026-01-19 9:45 ` Tomas Melin
2026-01-08 12:51 ` [PATCH v2 4/5] rtc: zynqmp: rework set_offset Tomas Melin
2026-01-14 15:37 ` T, Harini
2026-01-15 7:24 ` Tomas Melin
2026-01-08 12:51 ` [PATCH v2 5/5] rtc: zynqmp: use dynamic max and min offset ranges Tomas Melin
2026-01-14 15:37 ` T, Harini
2026-01-14 15:44 ` [PATCH v2 0/5] rtc: zynqmp: fixes for read and set offset T, Harini
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=fded3e4f-f292-48bf-aea7-0c8e71f7e056@vaisala.com \
--to=tomas.melin@vaisala.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=monstr@monstr.eu \
--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 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®