From: Nathan Lynch <ntl@pobox.com>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: Beginning Merger Patch
Date: Tue, 2 Aug 2005 21:17:42 -0500 [thread overview]
Message-ID: <20050803021742.GB3985@otto> (raw)
In-Reply-To: <1123023575.2614.25.camel@cashmere.sps.mot.com>
Jon Loeliger wrote:
> Folks,
>
> I have grabbed my asbestos suit.
>
> Here is a patch to begin the process of merging
> the PPC32 and PPC64 include directories into a
> new common "powerpc" arch.
Perhaps you could briefly explain the motivation for this?
I think I've heard/read that something like this was in the works, but
I'd like to know what the problem is, and why it should be solved this
way instead of e.g. x86_64's method of including headers directly from
asm-i386.
Nathan
next prev parent reply other threads:[~2005-08-03 2:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 22:59 Beginning Merger Patch Jon Loeliger
2005-08-02 23:05 ` Eugene Surovegin
2005-08-02 23:12 ` Dan Malek
2005-08-02 23:17 ` Eugene Surovegin
2005-08-03 3:08 ` Paul Mackerras
2005-08-03 2:38 ` Josh Boyer
2005-08-02 23:10 ` Dan Malek
2005-08-05 7:47 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 7:50 ` [PATCH] 2/2 merge the easy ones Stephen Rothwell
2005-08-05 8:37 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 9:08 ` Michael Ellerman
2005-08-05 11:53 ` Arnd Bergmann
2005-08-05 14:59 ` Stephen Rothwell
2005-08-05 16:24 ` Arnd Bergmann
2005-08-26 20:55 ` Jon Loeliger
2005-08-29 15:44 ` Segher Boessenkool
2005-08-29 18:41 ` Christopher Friesen
2005-08-17 5:39 ` Kumar Gala
2005-08-17 11:05 ` Arnd Bergmann
2005-08-03 2:17 ` Nathan Lynch [this message]
2005-08-03 2:58 ` Beginning Merger Patch Eugene Surovegin
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=20050803021742.GB3985@otto \
--to=ntl@pobox.com \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).