All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC, WIP, v7 3/4] media: vidtv: add a bridge driver
Date: Tue, 09 Jun 2020 08:29:05 +0800	[thread overview]
Message-ID: <202006090840.IfDCTHoX%lkp@intel.com> (raw)
In-Reply-To: <20200608191333.1784963-4-dwlsalmeida@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

Hi "Daniel,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linuxtv-media/master]
[cannot apply to linux/master v5.7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Daniel-W-S-Almeida/media-vidtv-implement-a-virtual-DVB-driver/20200609-031704
base:   git://linuxtv.org/media_tree.git master
config: mips-allyesconfig (attached as .config)
compiler: mips-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=mips 

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 <<):

mips-linux-ld: drivers/media/test-drivers/vidtv/vidtv_mux.o: in function `vidtv_mux_tick':
>> vidtv_mux.c:(.text.vidtv_mux_tick+0x83c): undefined reference to `__udivdi3'
>> mips-linux-ld: vidtv_mux.c:(.text.vidtv_mux_tick+0x864): undefined reference to `__udivdi3'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65686 bytes --]

  parent reply	other threads:[~2020-06-09  0:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 19:13 [RFC, WIP, v7 0/4] media: vidtv: implement a virtual DVB driver Daniel W. S. Almeida
2020-06-08 19:13 ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2020-06-08 19:13 ` [RFC, WIP, v7 1/4] media: vidtv: implement a tuner driver Daniel W. S. Almeida
2020-06-08 19:13   ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2020-06-08 19:13 ` [RFC, WIP, v7 2/4] media: vidtv: implement a demodulator driver Daniel W. S. Almeida
2020-06-08 19:13   ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2020-06-08 19:13 ` [RFC, WIP, v7 3/4] media: vidtv: add a bridge driver Daniel W. S. Almeida
2020-06-08 19:13   ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2020-06-08 21:17   ` kernel test robot
2020-06-09  0:29   ` kernel test robot [this message]
2020-06-08 19:13 ` [RFC, WIP, v7 4/4] media: Documentation: vidtv: Add ReST documentation for vidtv Daniel W. S. Almeida
2020-06-08 19:13   ` [Linux-kernel-mentees] " Daniel W. S. Almeida
2020-07-24 23:43 ` [RFC, WIP, v7 0/4] media: vidtv: implement a virtual DVB driver Shuah Khan
2020-07-24 23:43   ` [Linux-kernel-mentees] " Shuah Khan
2020-07-25 18:25   ` Mauro Carvalho Chehab
2020-07-25 18:25     ` [Linux-kernel-mentees] " Mauro Carvalho Chehab

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=202006090840.IfDCTHoX%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.