From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
virtualization@lists.osdl.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 4/6] Rename the parainstructions symbols to be consistent with the others
Date: Wed, 04 Apr 2007 12:03:17 +1000 [thread overview]
Message-ID: <1175652197.12230.563.camel@localhost.localdomain> (raw)
In-Reply-To: <20070404011453.598418421@goop.org>
On Tue, 2007-04-03 at 18:06 -0700, Jeremy Fitzhardinge wrote:
> plain text document attachment (fix-parainstructions-name.patch)
> The other symbols used to delineate the alt-instructions sections have
> the form __foo/__foo_end. Rename parainstructions to match.
OK, I guess this is an area where the kernel has its own standard.
(__start_<secname> and __stop_<secname> are the symbols automatically
inserted by ld if the section name is straight alpha-numeric. It's
actually pretty cool for code where you want section boundaries without
writing a linker script).
Cheers,
Rusty.
next prev parent reply other threads:[~2007-04-04 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 1:06 [patch 0/6] Various cleanups Jeremy Fitzhardinge
2007-04-04 1:06 ` [patch 1/6] Re-enable VDSO by default with PARAVIRT Jeremy Fitzhardinge
2007-04-04 16:57 ` Andi Kleen
2007-04-04 17:12 ` Jeremy Fitzhardinge
2007-04-04 1:06 ` [patch 2/6] Remove noreplacement option Jeremy Fitzhardinge
2007-04-04 1:06 ` [patch 3/6] Remove smp_alt_instructions Jeremy Fitzhardinge
2007-04-04 1:06 ` [patch 4/6] Rename the parainstructions symbols to be consistent with the others Jeremy Fitzhardinge
2007-04-04 2:03 ` Rusty Russell [this message]
2007-04-10 18:07 ` Andi Kleen
2007-04-10 18:44 ` Andrew Morton
2007-04-04 1:07 ` [patch 5/6] Allow boot-time disable of SMP altinstructions Jeremy Fitzhardinge
2007-04-04 1:07 ` [patch 6/6] Allow boot-time disable of paravirt_ops patching 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=1175652197.12230.563.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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).