From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Sep 15 (drivers/media/test-drivers/vidtv/)
Date: Tue, 15 Sep 2020 18:47:51 +0200 [thread overview]
Message-ID: <20200915184751.2d680848@coco.lan> (raw)
In-Reply-To: <55ef0376-7809-c875-5dcc-5bb46d6204df@infradead.org>
Hi Randy,
Em Tue, 15 Sep 2020 09:33:14 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:
> 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'
Geert already pointed those issues.
Daniel should be working on a fix. Hopefully we'll have a fixup patch
tomorrow.
Thanks,
Mauro
prev parent reply other threads:[~2020-09-15 17:29 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 ` linux-next: Tree for Sep 15 (drivers/media/test-drivers/vidtv/) Randy Dunlap
2020-09-15 16:47 ` Mauro Carvalho Chehab [this message]
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=20200915184751.2d680848@coco.lan \
--to=mchehab@kernel.org \
--cc=dwlsalmeida@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).