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>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for May 8 (drivers/media/pci/meye/)
Date: Wed, 8 May 2019 13:22:56 -0700 [thread overview]
Message-ID: <f4242ed8-971e-7d07-7df9-628c40d7dbf7@infradead.org> (raw)
In-Reply-To: <20190508173403.6088d0db@canb.auug.org.au>
On 5/8/19 12:34 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190507:
>
> The ubifs tree gained a conflict against Linus' tree.
>
Hi Mauro,
Commit 6159e12e11770fb25e748af90f6c5206c1df09ee:
media: meye: allow building it with COMPILE_TEST on non-x86
causes a build failure when
CONFIG_VIDEO_MEYE=y
CONFIG_SONY_LAPTOP=m
ld: drivers/media/pci/meye/meye.o: in function `meye_s_ctrl':
meye.c:(.text+0x5bb): undefined reference to `sony_pic_camera_command'
ld: meye.c:(.text+0x5db): undefined reference to `sony_pic_camera_command'
ld: meye.c:(.text+0x5fb): undefined reference to `sony_pic_camera_command'
ld: meye.c:(.text+0x61b): undefined reference to `sony_pic_camera_command'
ld: meye.c:(.text+0x63b): undefined reference to `sony_pic_camera_command'
ld: drivers/media/pci/meye/meye.o:meye.c:(.text+0x65b): more undefined references to `sony_pic_camera_command' follow
--
~Randy
next prev parent reply other threads:[~2019-05-08 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 7:34 linux-next: Tree for May 8 Stephen Rothwell
2019-05-08 20:22 ` Randy Dunlap [this message]
2019-05-08 20:43 ` linux-next: Tree for May 8 (drivers/platform/x86/intel_pmc_core_plat_drv.c) Randy Dunlap
2019-05-08 21:21 ` Andy Shevchenko
2019-05-08 21:54 ` Randy Dunlap
2019-05-08 23:15 ` Rajat Jain
2019-06-11 19:06 ` Andy Shevchenko
2019-06-28 3:37 ` Rajat Jain
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=f4242ed8-971e-7d07-7df9-628c40d7dbf7@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.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).