From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: Andrew Morton <akpm@osdl.org>,
Virtualization <virtualization@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Translate asm version of ELFNOTE macro into preprocessor macro
Date: Wed, 23 Aug 2006 14:02:52 -0700 [thread overview]
Message-ID: <44ECC27C.2020401@goop.org> (raw)
In-Reply-To: <1156362207.19808.69.camel@localhost.localdomain>
Ian Campbell wrote:
> Surprisingly string concatenation doesn't appear to be required for the
> majority of punctuation, at least so far as I can tell with this test
> patch (this is a xen-unstable kernel I had lying around so don't pay too
> much attention to head-xen.S bit). The only problem I found is comma,
> which can't be escaped.
>
> I've no idea how reliably this works across tool chain versions etc
> though. It worked for me ;-)
>
I guess that's a broad enough selection of names. I had assumed it
would impose normal symbol-like restrictions on the unquoted section
name. (I guess ';' would also need quoting.)
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@XenSource.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@osdl.org>,
Virtualization <virtualization@lists.osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Translate asm version of ELFNOTE macro into preprocessor macro
Date: Wed, 23 Aug 2006 14:02:52 -0700 [thread overview]
Message-ID: <44ECC27C.2020401@goop.org> (raw)
In-Reply-To: <1156362207.19808.69.camel@localhost.localdomain>
Ian Campbell wrote:
> Surprisingly string concatenation doesn't appear to be required for the
> majority of punctuation, at least so far as I can tell with this test
> patch (this is a xen-unstable kernel I had lying around so don't pay too
> much attention to head-xen.S bit). The only problem I found is comma,
> which can't be escaped.
>
> I've no idea how reliably this works across tool chain versions etc
> though. It worked for me ;-)
>
I guess that's a broad enough selection of names. I had assumed it
would impose normal symbol-like restrictions on the unquoted section
name. (I guess ';' would also need quoting.)
J
next prev parent reply other threads:[~2006-08-23 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 11:49 [PATCH] Translate asm version of ELFNOTE macro into preprocessor macro Ian Campbell
2006-08-23 14:49 ` Jeremy Fitzhardinge
2006-08-23 15:14 ` Ian Campbell
2006-08-23 15:23 ` Jeremy Fitzhardinge
2006-08-23 17:11 ` Eric W. Biederman
2006-08-23 17:47 ` Jeremy Fitzhardinge
2006-08-23 17:47 ` Jeremy Fitzhardinge
2006-08-23 19:43 ` Ian Campbell
2006-08-23 19:43 ` Ian Campbell
2006-08-23 21:02 ` Jeremy Fitzhardinge [this message]
2006-08-23 21:02 ` 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=44ECC27C.2020401@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@XenSource.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--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 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.