From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: bcrl@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] compile fix for fs/aio.c on non-highmem systems
Date: Fri, 30 Aug 2002 16:36:56 -0700 (PDT) [thread overview]
Message-ID: <20020830.163656.76075937.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208301641150.5430-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Fri, 30 Aug 2002 16:42:39 -0700 (PDT)
I don't really much care how it gets fixed, I could equally well imagine
having a dummy struct when CONFIG_HIGHMEM isn't set. Whatever makes the
dang thing work. There's certainly a good argument that non-broken
architectures shouldn't need to bother with kmap() at all..
Or that since the enumeration values are basically identical
on every system that the belong in linux/kmap_types.h :-)
next prev parent reply other threads:[~2002-08-30 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 21:53 [PATCH] compile fix for fs/aio.c on non-highmem systems Benjamin LaHaise
2002-08-30 23:21 ` David S. Miller
2002-08-30 23:42 ` Linus Torvalds
2002-08-30 23:36 ` David S. Miller [this message]
2002-09-03 17:06 ` Benjamin LaHaise
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=20020830.163656.76075937.davem@redhat.com \
--to=davem@redhat.com \
--cc=bcrl@redhat.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