From: Christoph Hellwig <hch@infradead.org>
To: Jeff Dike <jdike@karaya.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
jdike@ccure.karaya.com
Subject: Re: [PATCH] UML - part 1 of 2
Date: Mon, 22 Jul 2002 18:38:44 +0100 [thread overview]
Message-ID: <20020722183844.A8526@infradead.org> (raw)
In-Reply-To: <200207221715.MAA03040@ccure.karaya.com>; from jdike@karaya.com on Mon, Jul 22, 2002 at 12:15:29PM -0500
On Mon, Jul 22, 2002 at 12:15:29PM -0500, Jeff Dike wrote:
> include/linux/linkage.h -
> UML needs FASTCALL defined as regparm(3), too.
The fastcall definition should go into an asm/ header instead of such hacks..
the disk accounting stuff is also bogus - instead of wasting ram with
huge array it should rather be dynamically-allocated in a per-disk
structure..
next prev parent reply other threads:[~2002-07-22 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 17:15 [PATCH] UML - part 1 of 2 Jeff Dike
2002-07-22 17:38 ` Christoph Hellwig [this message]
2002-07-22 17:50 ` Alexander Viro
2002-07-22 18:06 ` Marcin Dalecki
2002-07-22 20:02 ` Jeff Dike
2002-07-22 19:08 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 23:16 Jeff Dike
2002-07-18 2:20 Jeff Dike
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=20020722183844.A8526@infradead.org \
--to=hch@infradead.org \
--cc=jdike@ccure.karaya.com \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--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