From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: kai@tp1.ruhr-uni-bochum.de, torvalds@transmeta.com, ak@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5.22] fix x86 initrd breakage
Date: Tue, 18 Jun 2002 03:53:12 +0200 [thread overview]
Message-ID: <20020618035312.A6714@wotan.suse.de> (raw)
In-Reply-To: <200206180055.CAA11524@harpo.it.uu.se>
> The patch below reverts the statement to its pre-2.5.17 state.
> Perhaps it should be removed altogether?
>
> Cc: to Andi Kleen since it seems x86_64 also is affected by
> this bug.
Thanks. I removed that statement for x86-64 from my tree.
-Andi
>
> --- linux-2.5.22/arch/i386/boot/Makefile.~1~ Tue Jun 11 14:18:07 2002
> +++ linux-2.5.22/arch/i386/boot/Makefile Tue Jun 18 00:43:12 2002
> @@ -23,7 +23,7 @@
>
> # If you want the RAM disk device, define this to be the size in blocks.
>
> -RAMDISK := -DRAMDISK=512
> +#RAMDISK := -DRAMDISK=512
prev parent reply other threads:[~2002-06-18 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 0:55 Mikael Pettersson
2002-06-18 1:53 ` Andi Kleen [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=20020618035312.A6714@wotan.suse.de \
--to=ak@suse.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®