From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Ian Campbell <Ian.Campbell@xensource.com>,
Andrew Morton <akpm@osdl.org>,
Ian Pratt <ian.pratt@xensource.com>,
Xen-devel <xen-devel@lists.xensource.com>,
Chris Wright <chrisw@sous-sol.org>,
Virtualization <virtualization@lists.osdl.org>,
Christoph Lameter <clameter@sgi.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux II
Date: Tue, 22 Aug 2006 08:13:59 -0700 [thread overview]
Message-ID: <44EB1F37.6030902@goop.org> (raw)
In-Reply-To: <200608221659.18896.ak@suse.de>
Andi Kleen wrote:
> Sorry I tried to apply it, but at least 2.6.18rc4 mainline (which my tree
> is based on) doesn't have a NOTES macro so it doesn't link
>
> I dropped the NOTES addition for now, presumably it will need to be readded
> later.
Yes, Ian's patch is incremental on top of mine, which defines the NOTES
macro in include/asm-generic/vmlinux.lds.h:
#define NOTES \
.notes : { *(.note.*) } :note
J
next prev parent reply other threads:[~2006-08-22 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:26 [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux Ian Campbell
2006-08-22 14:26 ` Ian Campbell
2006-08-22 14:48 ` Andi Kleen
2006-08-22 14:48 ` Andi Kleen
2006-08-22 14:59 ` [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux II Andi Kleen
2006-08-22 14:59 ` Andi Kleen
2006-08-22 15:13 ` Jeremy Fitzhardinge [this message]
2006-08-22 15:26 ` Ian Campbell
2006-08-22 15:26 ` Ian Campbell
2006-08-22 15:11 ` [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment in vmlinux Jeremy Fitzhardinge
2006-08-22 15:11 ` 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=44EB1F37.6030902@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@xensource.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=clameter@sgi.com \
--cc=ebiederm@xmission.com \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.