From: Christoph Hellwig <hch@infradead.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.2-rc1-mm1
Date: Thu, 22 Jan 2004 12:00:29 +0000 [thread overview]
Message-ID: <20040122120029.A9758@infradead.org> (raw)
In-Reply-To: <200401221217.i0MCHmeS001953@ccure.user-mode-linux.org>; from jdike@addtoit.com on Thu, Jan 22, 2004 at 07:17:48AM -0500
On Thu, Jan 22, 2004 at 07:17:48AM -0500, Jeff Dike wrote:
> hch@infradead.org said:
> > And this one brings in perfectly broken 2.4 block drivers.
>
> Can you be specific?
Try compiling the cow driver. Or look at the utter devfs mess in ubd.
In fact I wonder why the mail on that devfs abuse that I sent to uml-devel
about half a year ago is still unanswered.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-22 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 9:35 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 11:03 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 15:19 ` 2.6.2-rc1-mm1 viro
2004-01-22 20:31 ` 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 21:30 ` 2.6.2-rc1-mm1 Adrian Bunk
2004-01-22 23:38 ` 2.6.2-rc1-mm1 Greg KH
2004-01-23 0:24 ` 2.6.2-rc1-mm1 viro
2004-01-23 0:41 ` 2.6.2-rc1-mm1 Greg KH
2004-01-22 11:05 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:07 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:12 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 12:17 ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 12:00 ` Christoph Hellwig [this message]
2004-01-22 13:28 ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 16:26 ` 2.6.2-rc1-mm1 (compile stats) John Cherry
2004-01-22 21:12 ` 2.6.2-rc1-mm1 Tom Rini
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=20040122120029.A9758@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox