From: "H. Peter Anvin" <hpa@zytor.com>
To: Christian Ruppert <christian.ruppert@abilis.com>,
Pavel Roskin <proski@gnu.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Noam Camus <noamc@ezchip.com>
Subject: Re: [PATCH 2/2] x86: Add support for uncompressed kernel images
Date: Thu, 14 Nov 2013 09:31:44 -0800 [thread overview]
Message-ID: <52850900.2080101@zytor.com> (raw)
In-Reply-To: <1384418296-10374-2-git-send-email-christian.ruppert@abilis.com>
So it sounds like we're starting from the beginning - I presume that
means the patch currently in the kernel should be reverted first?
-hpa
next prev parent reply other threads:[~2013-11-14 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 16:34 Uncompressed kernel doesn't build on x86_64 Pavel Roskin
2013-11-13 16:49 ` H. Peter Anvin
2013-11-14 8:32 ` Christian Ruppert
2013-11-14 8:38 ` [PATCH 1/2] init/Kconfig: add option to disable kernel compression Christian Ruppert
2013-11-14 10:21 ` Vineet Gupta
2013-11-15 16:57 ` Christian Ruppert
2013-11-16 9:41 ` Vineet Gupta
2013-11-14 8:38 ` [PATCH 2/2] x86: Add support for uncompressed kernel images Christian Ruppert
2013-11-14 17:31 ` H. Peter Anvin [this message]
2013-11-15 9:31 ` Christian Ruppert
2013-11-14 17:45 ` H. Peter Anvin
2013-11-15 9:49 ` Christian Ruppert
2013-11-15 10:06 ` H. Peter Anvin
2013-11-14 14:13 ` Uncompressed kernel doesn't build on x86_64 Austin S Hemmelgarn
2013-11-14 23:38 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2013-11-18 9:48 [PATCH] [FIX] init/Kconfig: fix option to disable kernel compression Christian Ruppert
2013-11-18 9:51 ` [PATCH 2/2] x86: Add support for uncompressed kernel images Christian Ruppert
2013-11-18 11:25 ` Borislav Petkov
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=52850900.2080101@zytor.com \
--to=hpa@zytor.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=christian.ruppert@abilis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamc@ezchip.com \
--cc=proski@gnu.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 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.