From: Christoph Rohland <cr@sap.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Padraig Brady <padraig@antefacto.com>,
"Roy S.C. Ho" <scho1208@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: question about kernel 2.4 ramdisk
Date: 17 Dec 2001 08:55:44 +0100 [thread overview]
Message-ID: <m34rmq2scf.fsf@linux.local> (raw)
In-Reply-To: <3C0D2843.5060708@antefacto.com> <E16BLxI-0003Ic-00@the-village.bc.nu> <snaqhzhj.wl@nisaaru.dvs.cs.fujitsu.co.jp> <m3wv02oz2w.fsf@linux.local> <20011206173755.D16513@zax> <m3snamhwle.fsf@linux.local> <20011214063559.J18103@zax> <m3bsh07rd6.fsf@linux.local> <20011217144929.Q30975@zax>
In-Reply-To: <20011217144929.Q30975@zax>
Hi David,
On Mon, 17 Dec 2001, David Gibson wrote:
> I don't think there's a lot of point playing with this in 2.4.x. In
> 2.5 it depends a bit on what changes to the VFS happen.
I know and it was not meant for inclusion into 2.4. But 2.5 is not the
nicest target to test ideas right now ;-)
Greetings
Christoph
next prev parent reply other threads:[~2001-12-17 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 19:01 question about kernel 2.4 ramdisk Roy S.C. Ho
2001-12-04 19:47 ` Padraig Brady
2001-12-04 20:14 ` Alan Cox
2001-12-05 7:49 ` Christoph Rohland
2001-12-05 7:56 ` Tachino Nobuhiro
2001-12-05 8:23 ` Christoph Rohland
2001-12-05 8:42 ` Tachino Nobuhiro
2001-12-05 13:51 ` Christoph Rohland
2001-12-06 16:37 ` David Gibson
2001-12-06 16:55 ` Alan Cox
2001-12-08 9:53 ` Christoph Rohland
2001-12-14 5:35 ` David Gibson
2001-12-16 15:34 ` Christoph Rohland
2001-12-17 3:49 ` David Gibson
2001-12-17 7:55 ` Christoph Rohland [this message]
2001-12-05 9:37 ` Roy S.C. Ho
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=m34rmq2scf.fsf@linux.local \
--to=cr@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig@antefacto.com \
--cc=scho1208@yahoo.com \
--cc=tachino@open.nm.fujitsu.co.jp \
/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.