From: Andi Kleen <ak@suse.de>
To: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Consoldidate arch/{i386,x86_64}/boot/compressed/misc.c
Date: Tue, 23 May 2006 02:19:55 +0200 [thread overview]
Message-ID: <200605230219.56068.ak@suse.de> (raw)
In-Reply-To: <44720BD2.7060809@gmx.net>
On Monday 22 May 2006 21:06, Carl-Daniel Hailfinger wrote:
> Andi Kleen wrote:
>
> >> Would a series of incremental patches to consolidate these two
> >> subtrees get accepted?
> >>
> >
> > Yes.
> >
> > I have some plans to change the 64bit boot up though - the uncompression
> > should already run as 64bit - but that shouldnt' affect these files.
> >
>
> Clean up arch/{i386,x86_64}/boot/compressed/misc.c a bit to reduce their
> differences. Should have zero effect on code generation.
Applied.
-Andi
next prev parent reply other threads:[~2006-05-23 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 18:04 [RFC] Consoldidate arch/{i386,x86_64}/boot Carl-Daniel Hailfinger
2006-05-22 18:28 ` 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 [this message]
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=200605230219.56068.ak@suse.de \
--to=ak@suse.de \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--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