From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Vivek Goyal <vgoyal@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
v12n <virtualization@lists.linux-foundation.org>
Subject: [PATCH 5/9] add WEAK() for creating weak asm labels
Date: Wed, 20 Jun 2007 16:17:31 -0700 [thread overview]
Message-ID: <20070620231852.936240603@goop.org> (raw)
In-Reply-To: 20070620231726.834538992@goop.org
[-- Attachment #1: weak-linkage.patch --]
[-- Type: text/plain, Size: 467 bytes --]
Signed-off-by: Jeremy Fitzhardinge <jeremy@xensource.com>
---
include/linux/linkage.h | 6 ++++++
1 file changed, 6 insertions(+)
===================================================================
--- a/include/linux/linkage.h
+++ b/include/linux/linkage.h
@@ -34,6 +34,12 @@
name:
#endif
+#ifndef WEAK
+#define WEAK(name) \
+ .weak name; \
+ name:
+#endif
+
#define KPROBE_ENTRY(name) \
.pushsection .kprobes.text, "ax"; \
ENTRY(name)
--
next prev parent reply other threads:[~2007-06-20 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 23:17 [PATCH 0/9] x86 boot protocol updates Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 1/9] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 2/9] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 3/9] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 4/9] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-20 23:17 ` Jeremy Fitzhardinge [this message]
2007-06-20 23:17 ` [PATCH 6/9] always allocate space for notes Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 7/9] i386: paravirt boot sequence Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 8/9] ask the hypervisor how much space it needs reserved Jeremy Fitzhardinge
2007-06-20 23:17 ` [PATCH 9/9] xen: use boot protocol to boot xen kernel 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=20070620231852.936240603@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
--cc=virtualization@lists.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;
as well as URLs for NNTP newsgroup(s).