From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>,
Tony Lindgren <tony@atomide.com>, Dave Gerlach <d-gerlach@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Arnd Bergmann <arnd@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@gooogle.com>
Subject: Re: [PATCH] ARM: avoid cpuidle link warning
Date: Fri, 4 Jun 2021 11:02:37 -0700 [thread overview]
Message-ID: <162282975447.3081447.17719954433562444000.b4-ty@chromium.org> (raw)
In-Reply-To: <20201230155506.1085689-1-arnd@kernel.org>
On Wed, 30 Dec 2020 16:54:56 +0100, Arnd Bergmann wrote:
> Since commit 83109d5d5fba ("x86/build: Warn on orphan section placement"),
> we get a warning for objects in orphan sections. The cpuidle implementation
> for OMAP causes this when CONFIG_CPU_IDLE is disabled:
>
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
>
> [...]
Applied to for-next/orphans, thanks!
[1/1] ARM: cpuidle: Avoid orphan section warning
https://git.kernel.org/kees/c/d94b93a91015
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Russell King <linux@armlinux.org.uk>,
Tony Lindgren <tony@atomide.com>, Dave Gerlach <d-gerlach@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Arnd Bergmann <arnd@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@gooogle.com>
Subject: Re: [PATCH] ARM: avoid cpuidle link warning
Date: Fri, 4 Jun 2021 11:02:37 -0700 [thread overview]
Message-ID: <162282975447.3081447.17719954433562444000.b4-ty@chromium.org> (raw)
In-Reply-To: <20201230155506.1085689-1-arnd@kernel.org>
On Wed, 30 Dec 2020 16:54:56 +0100, Arnd Bergmann wrote:
> Since commit 83109d5d5fba ("x86/build: Warn on orphan section placement"),
> we get a warning for objects in orphan sections. The cpuidle implementation
> for OMAP causes this when CONFIG_CPU_IDLE is disabled:
>
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
> arm-linux-gnueabi-ld: warning: orphan section `__cpuidle_method_of_table' from `arch/arm/mach-omap2/pm33xx-core.o' being placed in section `__cpuidle_method_of_table'
>
> [...]
Applied to for-next/orphans, thanks!
[1/1] ARM: cpuidle: Avoid orphan section warning
https://git.kernel.org/kees/c/d94b93a91015
--
Kees Cook
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-04 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:54 [PATCH] ARM: avoid cpuidle link warning Arnd Bergmann
2020-12-30 15:54 ` Arnd Bergmann
2020-12-30 22:59 ` Miguel Ojeda
2020-12-30 22:59 ` Miguel Ojeda
2020-12-30 23:03 ` Miguel Ojeda
2020-12-30 23:03 ` Miguel Ojeda
2021-01-05 20:20 ` Nick Desaulniers
2021-01-05 20:20 ` Nick Desaulniers
2021-05-06 19:59 ` Nick Desaulniers
2021-05-06 19:59 ` Nick Desaulniers
2021-06-04 18:02 ` Kees Cook [this message]
2021-06-04 18:02 ` Kees Cook
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=162282975447.3081447.17719954433562444000.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=d-gerlach@ti.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ndesaulniers@gooogle.com \
--cc=ojeda@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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.