From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Alain Knaff <alain@knaff.lu>, Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: tip: bzip2/lzma now in tip:x86/setup-lzma
Date: Wed, 18 Feb 2009 11:53:50 -0800 [thread overview]
Message-ID: <499C674E.8010903@zytor.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0902181127310.30241@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Even if it is true in general, I would not remove CONFIG_INITRAMFS_SOURCE
> and attached logic, unless it were a major burden on the maintainers.
> (I am not to quantify whether it is such a burden, or is not.)
Removing CONFIG_INITRAMFS_SOURCE et al is not an option. It's widely
used. Nor is it a technical issue.
-hpa
next prev parent reply other threads:[~2009-02-18 19:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 21:46 update8 [PATCH 2/5] init: bzip2 or lzma -compressed kernels and initrds Alain Knaff
2009-01-04 23:08 ` H. Peter Anvin
2009-01-04 23:12 ` Alain Knaff
2009-01-04 23:14 ` H. Peter Anvin
2009-01-04 23:21 ` Alain Knaff
2009-01-04 23:58 ` tip: bzip2/lzma now in tip:x86/setup-lzma H. Peter Anvin
2009-01-05 3:03 ` Sam Ravnborg
2009-01-05 5:09 ` H. Peter Anvin
2009-01-05 5:42 ` Sam Ravnborg
[not found] ` <49615136.9080900@knaff.lu>
[not found] ` <4961580A.1020301@zytor.com>
[not found] ` <4961A816.40302@knaff.lu>
[not found] ` <4961A997.10108@zytor.com>
[not found] ` <4961ADC5.6030108@knaff.lu>
[not found] ` <49622DE9.2010200@zytor.com>
[not found] ` <496240DF.2010102@knaff.lu>
[not found] ` <49624F6C.8010103@zytor.com>
[not found] ` <4962522F.20804@knaff.lu>
[not found] ` <496255B0.1050208@zytor.com>
2009-01-05 18:57 ` Alain Knaff
2009-01-05 19:36 ` H. Peter Anvin
2009-01-05 22:07 ` Alain Knaff
2009-01-05 22:11 ` H. Peter Anvin
2009-01-05 22:12 ` Alain Knaff
2009-01-05 22:59 ` H. Peter Anvin
2009-01-06 7:09 ` Alain Knaff
2009-01-06 7:21 ` Willy Tarreau
2009-01-06 7:22 ` H. Peter Anvin
2009-01-06 7:30 ` Alain Knaff
2009-01-06 21:57 ` [bzip2/lzma] fix for built-in initramfs issue Alain Knaff
2009-01-06 22:48 ` H. Peter Anvin
2009-01-06 22:50 ` Alain Knaff
2009-01-06 22:58 ` H. Peter Anvin
2009-01-06 22:58 ` Alain Knaff
2009-01-06 7:18 ` tip: bzip2/lzma now in tip:x86/setup-lzma Jaswinder Singh Rajput
2009-01-06 7:24 ` H. Peter Anvin
2009-01-06 7:53 ` Jaswinder Singh Rajput
2009-01-06 8:27 ` H. Peter Anvin
2009-02-17 21:03 ` Jan Engelhardt
2009-02-17 21:05 ` H. Peter Anvin
2009-02-17 22:08 ` Ingo Molnar
2009-02-17 23:37 ` Ingo Molnar
2009-02-18 0:52 ` H. Peter Anvin
2009-02-18 7:48 ` Alain Knaff
2009-02-18 9:20 ` Jan Engelhardt
2009-02-18 9:40 ` Alain Knaff
2009-02-18 10:29 ` Jan Engelhardt
2009-02-18 19:53 ` H. Peter Anvin [this message]
2009-02-19 6:14 ` Alain Knaff
2009-02-19 14:46 ` H. Peter Anvin
2009-02-19 15:41 ` Alain Knaff
2009-02-19 18:03 ` H. Peter Anvin
2009-02-18 19:52 ` H. Peter Anvin
2009-02-18 21:09 ` Willy Tarreau
2009-02-19 20:11 ` Alain Knaff
2009-03-01 13:16 ` Alain Knaff
2009-03-01 19:27 ` H. Peter Anvin
2009-03-02 9:53 ` Ingo Molnar
2009-03-02 9:54 ` Alain Knaff
2009-03-02 10:22 ` Ingo Molnar
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=499C674E.8010903@zytor.com \
--to=hpa@zytor.com \
--cc=alain@knaff.lu \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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 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.