From: Conor Dooley <conor.dooley@microchip.com> To: Jisheng Zhang <jszhang@kernel.org> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Masahiro Yamada <masahiroy@kernel.org>, Kees Cook <keescook@chromium.org>, Nathan Chancellor <nathan@kernel.org>, Conor Dooley <conor@kernel.org>, <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 5/5] riscv: select ARCH_WANT_LD_ORPHAN_WARN for !XIP_KERNEL Date: Fri, 20 Jan 2023 08:06:43 +0000 [thread overview] Message-ID: <Y8pLk18Y+Jn4NI8f@wendy> (raw) In-Reply-To: <20230119155417.2600-6-jszhang@kernel.org> [-- Attachment #1: Type: text/plain, Size: 1065 bytes --] On Thu, Jan 19, 2023 at 11:54:17PM +0800, Jisheng Zhang wrote: > Now, after that all the sections are explicitly described and > declared in vmlinux.lds.S, we can enable ld orphan warnings for > !XIP_KERNEL to prevent from missing any new sections in future. > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> Warnings that the automation picked up are now gone in v2, thanks! Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > --- > arch/riscv/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index e2b656043abf..335e0c45cced 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -46,6 +46,7 @@ config RISCV > select ARCH_WANT_FRAME_POINTERS > select ARCH_WANT_GENERAL_HUGETLB > select ARCH_WANT_HUGE_PMD_SHARE if 64BIT > + select ARCH_WANT_LD_ORPHAN_WARN if !XIP_KERNEL > select ARCH_WANTS_THP_SWAP if HAVE_ARCH_TRANSPARENT_HUGEPAGE > select BINFMT_FLAT_NO_DATA_START_OFFSET if !MMU > select BUILDTIME_TABLE_SORT if MMU > -- > 2.38.1 > [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com> To: Jisheng Zhang <jszhang@kernel.org> Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Masahiro Yamada <masahiroy@kernel.org>, Kees Cook <keescook@chromium.org>, Nathan Chancellor <nathan@kernel.org>, Conor Dooley <conor@kernel.org>, <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 5/5] riscv: select ARCH_WANT_LD_ORPHAN_WARN for !XIP_KERNEL Date: Fri, 20 Jan 2023 08:06:43 +0000 [thread overview] Message-ID: <Y8pLk18Y+Jn4NI8f@wendy> (raw) In-Reply-To: <20230119155417.2600-6-jszhang@kernel.org> [-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --] On Thu, Jan 19, 2023 at 11:54:17PM +0800, Jisheng Zhang wrote: > Now, after that all the sections are explicitly described and > declared in vmlinux.lds.S, we can enable ld orphan warnings for > !XIP_KERNEL to prevent from missing any new sections in future. > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> Warnings that the automation picked up are now gone in v2, thanks! Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > --- > arch/riscv/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index e2b656043abf..335e0c45cced 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -46,6 +46,7 @@ config RISCV > select ARCH_WANT_FRAME_POINTERS > select ARCH_WANT_GENERAL_HUGETLB > select ARCH_WANT_HUGE_PMD_SHARE if 64BIT > + select ARCH_WANT_LD_ORPHAN_WARN if !XIP_KERNEL > select ARCH_WANTS_THP_SWAP if HAVE_ARCH_TRANSPARENT_HUGEPAGE > select BINFMT_FLAT_NO_DATA_START_OFFSET if !MMU > select BUILDTIME_TABLE_SORT if MMU > -- > 2.38.1 > [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] [-- Attachment #2: Type: text/plain, Size: 161 bytes --] _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-01-20 8:07 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-19 15:54 [PATCH v2 0/5] riscv: improve link and support ARCH_WANT_LD_ORPHAN_WARN Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-19 15:54 ` [PATCH v2 1/5] riscv: lds: define RUNTIME_DISCARD_EXIT Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-19 18:32 ` Conor Dooley 2023-01-19 18:32 ` Conor Dooley 2023-01-19 15:54 ` [PATCH v2 2/5] riscv: vmlinux.lds.S: explicitly catch .rela.dyn symbols Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-19 15:54 ` [PATCH v2 3/5] riscv: vmlinux.lds.S: explicitly catch .riscv.attributes sections Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-19 15:54 ` [PATCH v2 4/5] riscv: vmlinux.lds.S: explicitly catch .init.bss sections from EFI stub Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-19 15:54 ` [PATCH v2 5/5] riscv: select ARCH_WANT_LD_ORPHAN_WARN for !XIP_KERNEL Jisheng Zhang 2023-01-19 15:54 ` Jisheng Zhang 2023-01-20 8:06 ` Conor Dooley [this message] 2023-01-20 8:06 ` Conor Dooley 2023-02-22 15:00 ` [PATCH v2 0/5] riscv: improve link and support ARCH_WANT_LD_ORPHAN_WARN patchwork-bot+linux-riscv 2023-02-22 15:00 ` patchwork-bot+linux-riscv
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=Y8pLk18Y+Jn4NI8f@wendy \ --to=conor.dooley@microchip.com \ --cc=aou@eecs.berkeley.edu \ --cc=conor@kernel.org \ --cc=jszhang@kernel.org \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=masahiroy@kernel.org \ --cc=nathan@kernel.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.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: linkBe 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.