From: "Jan Beulich" <JBeulich@novell.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] minor ELF addition
Date: Wed, 09 Nov 2005 09:03:53 +0100 [thread overview]
Message-ID: <4371BB79.76F0.0078.0@novell.com> (raw)
In-Reply-To: <20051108145656.06e0d2b8.akpm@osdl.org>
>>> Andrew Morton <akpm@osdl.org> 08.11.05 23:56:56 >>>
>"Jan Beulich" <JBeulich@novell.com> wrote:
>>
>> A trivial addition to the ELF definitions.
>>
>> ...
>> #define STT_FILE 4
>> +#define STT_COMMON 5
>> +#define STT_TLS 6
>
>Is there any particular reason for adding these, or is it just a
>completeness thing?
NLKD needs STT_COMMON. STT_TLS is just for completeness (and probably
not of much use in the kernel, though Andi seemed to have at least
considered using TLS for x86-64's per-CPU data).
prev parent reply other threads:[~2005-11-09 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 12:54 Jan Beulich
2005-11-08 22:56 ` Andrew Morton
2005-11-09 8:03 ` Jan Beulich [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=4371BB79.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome