From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Virtualization <virtualization@lists.osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
Ian Pratt <ian.pratt@xensource.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1 of 1] x86_43: Put .note.* sections into a PT_NOTE segment in vmlinux
Date: Tue, 22 Aug 2006 12:43:09 +0100 [thread overview]
Message-ID: <1156246989.5091.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20060822133306.79fac714.ak@suse.de>
On Tue, 2006-08-22 at 13:33 +0200, Andi Kleen wrote:
> On Tue, 22 Aug 2006 12:14:18 +0100
> Ian Campbell <Ian.Campbell@XenSource.com> wrote:
>
> > On Tue, 2006-08-01 at 13:00 -0700, Jeremy Fitzhardinge wrote:
> > > This patch will pack any .note.* section into a PT_NOTE segment in the
> > > output file.
> > [...]
> > > This only changes i386 for now, but I presume the corresponding
> > > changes for other architectures will be as simple.
> >
> > Here is the patch for x86_64.
>
> Ok, but can you please resubmit with complete changelog/rationale?
Will do.
I've just noticed a bunch of sections (.vsyscall_*, .xtime and others)
which aren't getting put into segments for some reason. I'll figure that
out first...
Ian.
prev parent reply other threads:[~2006-08-22 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2bf2abf6e97048bbef24.1154462451@ezr>
2006-08-22 11:14 ` [PATCH 1 of 1] x86_43: Put .note.* sections into a PT_NOTE segment in vmlinux Ian Campbell
2006-08-22 11:33 ` Andi Kleen
2006-08-22 11:43 ` Ian Campbell [this message]
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=1156246989.5091.19.camel@localhost.localdomain \
--to=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=jeremy@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 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).