From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: randy.dunlap@verizon.net, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [PATCH] move SWAP option in menu
Date: Wed, 5 Mar 2003 13:14:44 -0800 [thread overview]
Message-ID: <20030305131444.1b9b0cf2.rddunlap@osdl.org> (raw)
In-Reply-To: <20030305181748.GA11729@iram.es>
On Wed, 5 Mar 2003 19:17:48 +0100 Gabriel Paubert <paubert@iram.es> wrote:
| On Tue, Mar 04, 2003 at 08:36:13PM -0800, Randy.Dunlap wrote:
| > Hi,
| >
| > Please apply this patch (option B of 2 choices) from
| > Tomas Szepe to move the SWAP option into the General Setup
| > menu.
| >
| > Patch is to 2.5.64.
| >
[snip]
|
| Why restrict it to Intel only? I don't know if it works properly on
| other architectures, but at least it would give people the opportunity
| to test it on embedded PPC/Arm/MIPS/CRIS/whatever.
|
| >From a quick grep over a recent BK tree, the only files who have
| sections conditional on CONFIG_SWAP are:
|
| include/linux/page-flags.h
| include/linux/swap.h
| mm/vmscan.c
| mm/Makefile
|
| no architecture specific code at all. From a quick look, the
| conditionals are rather simple (most of them are replacements of
| actual functions by dummies) and should work on all architectures.
| Please let people test it on non-X86, after all it's still a
| development kernel. Any breakage is unlikely to be serious and
| embedded people are going to be the most interested since it
| saves some space.
OK, please send a patch.
--
~Randy
next prev parent reply other threads:[~2003-03-05 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 4:36 [PATCH] move SWAP option in menu Randy.Dunlap
2003-03-05 18:17 ` Gabriel Paubert
2003-03-05 21:14 ` Randy.Dunlap [this message]
2003-03-06 18:43 ` Tom Rini
2003-03-06 18:49 ` Christoph Hellwig
2003-03-06 18:54 ` Tom Rini
2003-03-06 18:56 ` Christoph Hellwig
2003-03-06 19:33 ` Gabriel Paubert
2003-03-06 21:06 ` Alan Cox
2003-03-07 10:03 ` Gabriel Paubert
2003-03-07 12:41 ` Alan Cox
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=20030305131444.1b9b0cf2.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=randy.dunlap@verizon.net \
--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;
as well as URLs for NNTP newsgroup(s).