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-riscv <linux-riscv@lists.infradead.org>
Subject: Re: linux-next: Tree for Jan 2 (riscv: exittext undef. references)
Date: Tue, 2 Jan 2024 09:15:29 -0800 [thread overview]
Message-ID: <8693bf84-b3b5-407b-871f-4add127272ee@infradead.org> (raw)
In-Reply-To: <20240102165725.6d18cc50@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On 1/1/24 21:57, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20231222:
>
on riscv 64-bit:
(gcc 13.2.0)
riscv64-linux-ld: arch/riscv/kernel/patch.o: in function `.L8':
patch.c:(.text+0x17e): undefined reference to `__exittext_begin'
riscv64-linux-ld: patch.c:(.text+0x19c): undefined reference to `__exittext_end'
riscv64-linux-ld: arch/riscv/kernel/patch.o: in function `.L43':
patch.c:(.text+0x40a): undefined reference to `__exittext_begin'
riscv64-linux-ld: arch/riscv/kernel/patch.o: in function `.L0 ':
patch.c:(.text+0x428): undefined reference to `__exittext_end'
riscv64-linux-ld: patch.c:(.text+0xae8): undefined reference to `__exittext_begin'
riscv64-linux-ld: arch/riscv/kernel/patch.o: in function `.L82':
patch.c:(.text+0xb06): undefined reference to `__exittext_end'
riscv64-linux-ld: arch/riscv/kernel/patch.o: in function `.L118':
patch.c:(.text+0xd6e): undefined reference to `__exittext_begin'
riscv64-linux-ld: patch.c:(.text+0xd8c): undefined reference to `__exittext_end'
Full randconfig file is attached.
--
#Randy
[-- Attachment #2: config-r4502.gz --]
[-- Type: application/gzip, Size: 31928 bytes --]
next prev parent reply other threads:[~2024-01-02 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 5:57 linux-next: Tree for Jan 2 Stephen Rothwell
2024-01-02 17:02 ` linux-next: Tree for Jan 2 (net/ethernet/realtek/r8169) Randy Dunlap
2024-01-02 19:56 ` Heiner Kallweit
2024-01-02 17:15 ` Randy Dunlap [this message]
2024-01-04 11:02 ` linux-next: Tree for Jan 2 (riscv: exittext undef. references) Alexandre Ghiti
2024-01-02 18:07 ` linux-next: Tree for Jan 2 (riscv & KVM problem) Randy Dunlap
2024-01-03 15:18 ` Andrew Jones
2024-01-04 6:06 ` Randy Dunlap
2024-01-04 8:44 ` Andrew Jones
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=8693bf84-b3b5-407b-871f-4add127272ee@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.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
all inboxes | Powered by JetHome®