From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Thierry Reding <treding@nvidia.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sowjanya Komatineni <skomatineni@nvidia.com>
Subject: Re: linux-next: build failure after merge of the tegra tree
Date: Tue, 12 May 2020 23:12:07 +0200 [thread overview]
Message-ID: <20200512211207.GD3864641@ulmo> (raw)
In-Reply-To: <20200511085114.0cde64d9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On Mon, May 11, 2020 at 08:51:14AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tegra tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "host1x_driver_register_full" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_device_exit" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_client_unregister" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_driver_unregister" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_device_init" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_syncpt_free" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_syncpt_request" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
> ERROR: modpost: "host1x_client_register" [drivers/staging/media/tegra-video/tegra-video.ko] undefined!
>
> Caused by commit
>
> 423d10a99b30 ("media: tegra: Add Tegra210 Video input driver")
>
> I removed CONFIG_COMPILE_TEST for this driver for today.
Thanks, I've now added a patch that drops the alternative dependency on
COMPILE_TEST because TEGRA_HOST1X doesn't have stubs for any of these
exported functions.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-12 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 22:51 linux-next: build failure after merge of the tegra tree Stephen Rothwell
2020-05-12 21:12 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-04 23:39 Stephen Rothwell
2021-10-04 23:54 ` Dmitry Osipenko
2021-10-06 18:00 ` Thierry Reding
2021-10-06 18:27 ` Dmitry Osipenko
2025-11-14 1:30 Stephen Rothwell
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=20200512211207.GD3864641@ulmo \
--to=thierry.reding@gmail.com \
--cc=ccross@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
--cc=skomatineni@nvidia.com \
--cc=treding@nvidia.com \
/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.