From: kernel test robot <lkp@intel.com>
To: tumic@gpxsee.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Martin Tůma" <martin.tuma@digiteqautomotive.com>
Subject: Re: [PATCH v2 2/2] media: mgb4: Add support for V4L2_CAP_TIMEPERFRAME
Date: Sun, 10 Mar 2024 02:39:47 +0800 [thread overview]
Message-ID: <202403100204.fyBLGfk1-lkp@intel.com> (raw)
In-Reply-To: <20240307121822.1852-3-tumic@gpxsee.org>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on 65e6a2773d655172143cc0b927cdc89549842895]
url: https://github.com/intel-lab-lkp/linux/commits/tumic-gpxsee-org/media-mgb4-Add-support-for-YUV-image-formats/20240307-192243
base: 65e6a2773d655172143cc0b927cdc89549842895
patch link: https://lore.kernel.org/r/20240307121822.1852-3-tumic%40gpxsee.org
patch subject: [PATCH v2 2/2] media: mgb4: Add support for V4L2_CAP_TIMEPERFRAME
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20240310/202403100204.fyBLGfk1-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240310/202403100204.fyBLGfk1-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/202403100204.fyBLGfk1-lkp@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: drivers/media/pci/mgb4/mgb4_vin.o: in function `vidioc_s_parm':
>> mgb4_vin.c:(.text+0x1d64): undefined reference to `__aeabi_uldivmod'
>> arm-linux-gnueabi-ld: mgb4_vin.c:(.text+0x1e48): undefined reference to `__aeabi_uldivmod'
arm-linux-gnueabi-ld: drivers/media/pci/mgb4/mgb4_vout.o: in function `vidioc_s_parm':
>> mgb4_vout.c:(.text+0x183c): undefined reference to `__aeabi_uldivmod'
>> arm-linux-gnueabi-ld: mgb4_vout.c:(.text+0x1920): undefined reference to `__aeabi_uldivmod'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-09 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:18 [PATCH v2 0/2] media: mgb4: YUV and variable framerate support tumic
2024-03-07 12:18 ` [PATCH v2 1/2] media: mgb4: Add support for YUV image formats tumic
2024-03-07 12:18 ` [PATCH v2 2/2] media: mgb4: Add support for V4L2_CAP_TIMEPERFRAME tumic
2024-03-09 18:39 ` kernel test robot [this message]
2024-03-09 18:50 ` kernel test robot
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=202403100204.fyBLGfk1-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martin.tuma@digiteqautomotive.com \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tumic@gpxsee.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