public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: <mingo@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH] i386: fix a few paravirt-related modpost warnings
Date: Mon, 10 Dec 2007 16:38:44 +0000	[thread overview]
Message-ID: <475D79A4.76E4.0078.0@novell.com> (raw)

Signed-off-by: Jan Beulich <jbeulich@novell.com>

 arch/x86/kernel/head_32.S |    2 +-
 arch/x86/xen/setup.c      |    2 +-
 arch/x86/xen/xen-head.S   |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

--- linux-2.6.24-rc4/arch/x86/kernel/head_32.S	2007-12-07 09:00:59.000000000 +0100
+++ 2.6.24-rc4-i386-lguest-warning/arch/x86/kernel/head_32.S	2007-12-05 18:30:33.000000000 +0100
@@ -151,7 +151,7 @@ WEAK(xen_entry)
 	/* Unknown implementation; there's really
 	   nothing we can do at this point. */
 	ud2a
-.data
+.section .init.data, "aw"
 subarch_entries:
 	.long default_entry		/* normal x86/PC */
 	.long lguest_entry		/* lguest hypervisor */
--- linux-2.6.24-rc4/arch/x86/xen/setup.c	2007-12-07 09:01:00.000000000 +0100
+++ 2.6.24-rc4-i386-lguest-warning/arch/x86/xen/setup.c	2007-12-10 17:31:06.000000000 +0100
@@ -59,7 +59,7 @@ static void xen_idle(void)
 /*
  * Set the bit indicating "nosegneg" library variants should be used.
  */
-static void fiddle_vdso(void)
+static __init void fiddle_vdso(void)
 {
 	extern u32 VDSO_NOTE_MASK; /* See ../kernel/vsyscall-note.S.  */
 	extern char vsyscall_int80_start;
--- linux-2.6.24-rc4/arch/x86/xen/xen-head.S	2007-12-07 09:01:00.000000000 +0100
+++ 2.6.24-rc4-i386-lguest-warning/arch/x86/xen/xen-head.S	2007-12-10 17:25:46.000000000 +0100
@@ -7,7 +7,7 @@
 #include <asm/boot.h>
 #include <xen/interface/elfnote.h>
 
-.pushsection .init.text
+.pushsection .init.text, "ax"
 ENTRY(startup_xen)
 	movl %esi,xen_start_info
 	cld




             reply	other threads:[~2007-12-10 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 16:38 Jan Beulich [this message]
2007-12-11  0:34 ` [PATCH] i386: fix a few paravirt-related modpost warnings Jeremy Fitzhardinge

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=475D79A4.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox