From: Rusty Russell <rusty@rustcorp.com.au>
To: Chen Gang <gang.chen@asianux.com>,
James Hogan <james.hogan@imgtec.com>,
mmarek@suse.cz, Sam Ravnborg <sam@ravnborg.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] scripts/mod/modpost.c: permit '.cranges' secton for sh64 architecture.
Date: Fri, 02 Aug 2013 11:57:37 +0930 [thread overview]
Message-ID: <871u6c4yjq.fsf@rustcorp.com.au> (raw)
In-Reply-To: <51F9F5AB.6030002@asianux.com>
Chen Gang <gang.chen@asianux.com> writes:
> Need permit '.cranges' section for sh64 architecture, or modpost will
> report warning:
>
> LD init/built-in.o
> WARNING: init/built-in.o (.cranges): unexpected non-allocatable section.
> Did you forget to use "ax"/"aw" in a .S file?
> Note that for example <linux/init.h> contains
> section definitions for use in .S files.
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
Applied.
Thanks,
Rusty.
> ---
> scripts/mod/modpost.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 6216434..8247979 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -821,6 +821,7 @@ static const char *section_white_list[] =
> {
> ".comment*",
> ".debug*",
> + ".cranges", /* sh64 */
> ".zdebug*", /* Compressed debug sections. */
> ".GCC-command-line", /* mn10300 */
> ".GCC.command.line", /* record-gcc-switches, non mn10300 */
> --
> 1.7.7.6
next prev parent reply other threads:[~2013-08-02 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 5:44 [PATCH] scripts/mod/modpost.c: permit '.cranges' secton for sh64 architecture Chen Gang
2013-08-02 2:27 ` Rusty Russell [this message]
2013-08-02 4:01 ` Chen Gang
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=871u6c4yjq.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=gang.chen@asianux.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=paul.gortmaker@windriver.com \
--cc=sam@ravnborg.org \
/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