LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: paulus@samba.org
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: [POWERPC] iSeries: supress lparmap.c warning
Date: Mon, 18 Dec 2006 16:14:29 +1100	[thread overview]
Message-ID: <20061218161429.4ffeec4e.sfr@canb.auug.org.au> (raw)

lparmap.c: Assembler messages:
lparmap.c:43: Warning: ignoring changed section attributes for .text

We do not need the .section ops in the generated .s file, so
just remove them.

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/powerpc/kernel/Makefile  |    7 +++++--
 arch/powerpc/kernel/head_64.S |    2 +-
 2 files changed, 6 insertions(+), 3 deletions(-)

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --git a/arch/powerpc/kernel/Makefile b/arch/powerpc/kernel/Makefile
index d2ded19..0f7cb0b 100644
--- a/arch/powerpc/kernel/Makefile
+++ b/arch/powerpc/kernel/Makefile
@@ -76,9 +76,12 @@ obj-y				+= iomap.o
 endif
 
 ifeq ($(CONFIG_PPC_ISERIES),y)
-extra-y += lparmap.s
-$(obj)/head_64.o:	$(obj)/lparmap.s
+extra-y += lparmap.s lparmap1.s
+$(obj)/head_64.o:	$(obj)/lparmap1.s
 AFLAGS_head_64.o += -I$(obj)
+
+$(obj)/lparmap1.s:	$(obj)/lparmap.s
+	@grep -v '\.section' $< >$@
 endif
 
 else
diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
index 71b1fe5..b34e173 100644
--- a/arch/powerpc/kernel/head_64.S
+++ b/arch/powerpc/kernel/head_64.S
@@ -1535,7 +1535,7 @@ fwnmi_data_area:
 	 * both pSeries and iSeries */
 #ifdef CONFIG_PPC_ISERIES
         . = LPARMAP_PHYS
-#include "lparmap.s"
+#include "lparmap1.s"
 /*
  * This ".text" is here for old compilers that generate a trailing
  * .note section when compiling .c files to .s
-- 
1.4.4.2

             reply	other threads:[~2006-12-18  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  5:14 Stephen Rothwell [this message]
2006-12-18 10:41 ` [POWERPC] iSeries: supress lparmap.c warning Segher Boessenkool

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=20061218161429.4ffeec4e.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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