From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
linux-media <linux-media@vger•kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel•org>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail•com>
Subject: Re: linux-next: Tree for Sep 15 (drivers/media/test-drivers/vidtv/)
Date: Tue, 15 Sep 2020 09:33:14 -0700 [thread overview]
Message-ID: <55ef0376-7809-c875-5dcc-5bb46d6204df@infradead.org> (raw)
In-Reply-To: <20200915174932.3aa7d103@canb.auug.org.au>
On 9/15/20 12:49 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200914:
>
> The v4l-dvb tree lost its build failure.
>
media driver build problems on i386:
gcc (SUSE Linux) 7.5.0
build#1:
ERROR: modpost: "__udivdi3" [drivers/media/test-drivers/vidtv/dvb-vidtv-bridge.ko] undefined!
build#2:
ld: drivers/media/test-drivers/vidtv/vidtv_s302m.o: in function `vidtv_s302m_encode':
vidtv_s302m.c:(.text+0x1f3): undefined reference to `__udivdi3'
ld: drivers/media/test-drivers/vidtv/vidtv_mux.o: in function `vidtv_mux_tick':
vidtv_mux.c:(.text+0x3ee): undefined reference to `__udivdi3'
ld: vidtv_mux.c:(.text+0x40b): undefined reference to `__udivdi3'
randconfig files are available if anyone wants them.
thanks.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead•org>
next prev parent reply other threads:[~2020-09-15 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 7:49 linux-next: Tree for Sep 15 Stephen Rothwell
2020-09-15 16:33 ` Randy Dunlap [this message]
2020-09-15 16:47 ` linux-next: Tree for Sep 15 (drivers/media/test-drivers/vidtv/) 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=55ef0376-7809-c875-5dcc-5bb46d6204df@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=dwlsalmeida@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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