From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Andi Kleen <ak@suse.de>
Subject: [RFC] Consoldidate arch/{i386,x86_64}/boot
Date: Mon, 22 May 2006 20:04:36 +0200 [thread overview]
Message-ID: <4471FD34.8050202@gmx.net> (raw)
Hi,
there are many differences between the files in
arch/{i386,x86_64}/boot, but it seems most (if not all) of them
have no effect on the generated code and are purely cosmetical.
I have a patch which increases similarity between these
subtrees, while still generating identical code. After that,
only very few differences remain in
compressed/misc.c
video.S
tools/build.c
and it should be possible to unify them and kill one copy of
each.
Would a series of incremental patches to consolidate these two
subtrees get accepted?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next reply other threads:[~2006-05-22 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 18:04 Carl-Daniel Hailfinger [this message]
2006-05-22 18:28 ` [RFC] Consoldidate arch/{i386,x86_64}/boot Andi Kleen
2006-05-22 19:06 ` [PATCH] Consoldidate arch/{i386,x86_64}/boot/compressed/misc.c Carl-Daniel Hailfinger
2006-05-23 0:19 ` Andi Kleen
2006-05-23 3:09 ` Carl-Daniel Hailfinger
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=4471FD34.8050202@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=ak@suse.de \
--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