From: Pavel Machek <pavel@ucw.cz>
To: Norbert Kiesel <nkiesel@tbdnetworks.com>
Cc: "Alejandro Riveira Fernández" <ariveira@gmail.com>,
"Adrian Bunk" <bunk@stusta.de>,
"Arjan van de Ven" <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: Why is "Memory split" Kconfig option only for EMBEDDED?
Date: Thu, 14 Dec 2006 14:47:51 +0000 [thread overview]
Message-ID: <20061214144750.GA4022@ucw.cz> (raw)
In-Reply-To: <1165679105.7455.116.camel@titan.tbdnetworks.com>
Hi!
> So far all first-hand experiences I heard of were positive (i.e. I did
> not get an emaail from anyone saying: It had a negative effect for me),
> so I propose to apply the patch from Con Kolivas. The wording in the
> description still very strongly recommends to not change that value, and
> it's still dependent on EXPERIMENTAL. I append the patch just because
There's a big difference between 'experimental' and 'known to broke
obscure userspace apps'.
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-12-15 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 11:42 Why is "Memory split" Kconfig option only for EMBEDDED? Norbert Kiesel
2006-12-06 11:58 ` Arjan van de Ven
2006-12-06 12:19 ` Norbert Kiesel
2006-12-06 12:45 ` Arjan van de Ven
2006-12-06 13:36 ` Norbert Kiesel
2006-12-06 21:00 ` Jan Engelhardt
2006-12-06 21:10 ` Jan Engelhardt
2006-12-06 13:10 ` Adrian Bunk
2006-12-09 12:27 ` Alejandro Riveira Fernández
2006-12-09 15:45 ` Norbert Kiesel
2006-12-09 16:01 ` Adrian Bunk
2006-12-14 14:47 ` Pavel Machek [this message]
2006-12-14 15:24 ` Norbert Kiesel
-- strict thread matches above, loose matches on Subject: below --
2006-12-10 4:26 linux
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=20061214144750.GA4022@ucw.cz \
--to=pavel@ucw.cz \
--cc=ariveira@gmail.com \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nkiesel@tbdnetworks.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