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>,
Eugen Hristev <eugen.hristev@microchip.com>
Subject: Re: linux-next: Tree for Jul 9 (drivers/media/platform/atmel/atmel-isc-base.o)
Date: Fri, 9 Jul 2021 13:07:41 -0700 [thread overview]
Message-ID: <955c978d-842b-c5fd-6c1b-7e403ba6fe75@infradead.org> (raw)
In-Reply-To: <20210709132450.7aac126f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On 7/8/21 8:24 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.15 related material to your linux-next included
> branches until after v5.14-rc1 has been released.
>
> Changes since 20210708:
>
on x86_64:
ld: drivers/media/platform/atmel/atmel-isc-base.o: in function `isc_async_complete':
atmel-isc-base.c:(.text+0x2117): undefined reference to `__this_module'
ld: drivers/media/platform/atmel/atmel-isc-base.o:(.rodata+0x760): undefined reference to `__this_module'
ld: drivers/media/platform/atmel/atmel-isc-base.o:(__param+0x8): undefined reference to `__this_module'
ld: drivers/media/platform/atmel/atmel-isc-base.o:(__param+0x30): undefined reference to `__this_module'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-media-atmel-this-module.gz --]
[-- Type: application/gzip, Size: 33608 bytes --]
next prev parent reply other threads:[~2021-07-09 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 3:24 linux-next: Tree for Jul 9 Stephen Rothwell
2021-07-09 20:07 ` Randy Dunlap [this message]
2021-07-26 7:38 ` linux-next: Tree for Jul 9 (drivers/media/platform/atmel/atmel-isc-base.o) Eugen.Hristev
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=955c978d-842b-c5fd-6c1b-7e403ba6fe75@infradead.org \
--to=rdunlap@infradead.org \
--cc=eugen.hristev@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.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).