From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Zankel <czankel@tensilica.com>
Cc: torvalds@linux-foundation.org, chris@zankel.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix modpost warnings for xtensa
Date: Thu, 19 Jul 2007 14:00:05 -0700 [thread overview]
Message-ID: <20070719140005.863f7ffa.akpm@linux-foundation.org> (raw)
In-Reply-To: <200707191837.l6JIbuE25527@corvus.hq.tensilica.com>
On Thu, 19 Jul 2007 11:37:56 -0700
Chris Zankel <czankel@tensilica.com> wrote:
>
> [PATCH] fix modpost warnings for xtensa
>
> The Xtensa architecture places literal pools in sections separate
> from the instructions. The corresponsing text sections, therefore,
> reference the .literal section, and we have to suppress those
> warnings. The naming convention defines the name for a literal
> section as .SECTION.literal, unless .SECTION is .text. In that case
> the name is only .literal. Using strncmp() instead of strcmp()
> to compare the from-section with .SECTION.init.refok in pattern 0
> should not cause any regressions for other architectures.
> We also need to suppress warnings for two informational
> sections (.xt.lit and .xt.prop) used by the Xtensa architecture.
This generates unfixable-by-me rejects against Sam's git-kbuild tree.
Sam already had a pull request into Linus for that tree. Could I ask
that you wait for that piece of dust to settle and then regenerate the
diff?
Thanks.
next prev parent reply other threads:[~2007-07-19 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 18:37 [PATCH] fix modpost warnings for xtensa Chris Zankel
2007-07-19 21:00 ` Andrew Morton [this message]
2007-07-19 21:10 ` Chris Zankel
2007-07-25 20:29 ` Sam Ravnborg
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=20070719140005.863f7ffa.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=czankel@tensilica.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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