From: Chris Snook <csnook@redhat.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: about relocs.c on x86
Date: Thu, 31 Jan 2008 04:17:37 -0500 [thread overview]
Message-ID: <47A19231.9030302@redhat.com> (raw)
In-Reply-To: <86802c440801310113s4f792b70le8377440078125f4@mail.gmail.com>
Yinghai Lu wrote:
> On Jan 31, 2008 12:33 AM, Chris Snook <csnook@redhat.com> wrote:
>> Yinghai Lu wrote:
>>> why not rename relocs.c to relocs_32.c?
>> Because we're trying to get rid of all the _32 and _64 files?
>
> but that file is not need for x86_64
Which means there's no conflict with any 64-bit code, and thus no reason
to break it out into a _32 file.
-- Chris
next prev parent reply other threads:[~2008-01-31 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 8:07 about relocs.c on x86 Yinghai Lu
2008-01-31 8:33 ` Chris Snook
2008-01-31 9:13 ` Yinghai Lu
2008-01-31 9:17 ` Chris Snook [this message]
2008-01-31 9:52 ` Ingo Molnar
2008-01-31 10:02 ` Harvey Harrison
2008-01-31 10:11 ` Ingo Molnar
2008-01-31 10:21 ` Harvey Harrison
2008-01-31 10:38 ` Sam Ravnborg
2008-01-31 10:44 ` Harvey Harrison
2008-01-31 12:04 ` Ingo Molnar
2008-01-31 17:47 ` H. Peter Anvin
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=47A19231.9030302@redhat.com \
--to=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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.