From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@surriel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21pre5aa1
Date: Fri, 14 Mar 2003 18:35:50 +0100 [thread overview]
Message-ID: <20030314173550.GG1375@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0303140852220.27094-100000@dhcp64-226.boston.redhat.com>
On Fri, Mar 14, 2003 at 08:53:09AM -0500, Rik van Riel wrote:
> On Fri, 14 Mar 2003, Andrea Arcangeli wrote:
>
> > Only in 2.4.21pre4aa3: 9900_aio-17.gz
> > Only in 2.4.21pre5aa1: 9900_aio-18.gz
> >
> > Cleaned up the whole asm/kmap_types.h mess, moved
> > kmap_types.h into linux/, this must be visible
> > for aio and it has to be the same for all archs so it doesn't belong to
> > asm/.
>
> Maybe I'm dense, maybe it's early on a friday morning, maybe
> even both ... but I don't understand why architectures without
> highmem should have kmap_types.h
it's the aio code that does some kmap_atomic in the common code, and the
kmap_atomic pretends to get a km_type parameter. Of course the km_type
parameter is optimized away at compile time if highmem is disabled, but
this allows to use kmap_atomic in common code.
Andrea
prev parent reply other threads:[~2003-03-14 17:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 9:08 2.4.21pre5aa1 Andrea Arcangeli
2003-03-14 10:15 ` 2.4.21pre5aa1 Marc-Christian Petersen
2003-03-14 10:29 ` 2.4.21pre5aa1 Andrea Arcangeli
2003-03-14 12:50 ` 2.4.21pre5aa1 Andrew Morton
2003-03-14 17:27 ` 2.4.21pre5aa1 Andrea Arcangeli
2003-03-14 13:39 ` 2.4.21pre5aa1 Marc-Christian Petersen
2003-03-14 17:05 ` 2.4.21pre5aa1 Marc-Christian Petersen
2003-03-14 17:10 ` 2.4.21pre5aa1 Marc-Christian Petersen
2003-03-14 17:38 ` 2.4.21pre5aa1 Andrea Arcangeli
2003-03-14 18:04 ` 2.4.21pre5aa1 Marc-Christian Petersen
2003-03-14 23:13 ` 2.4.21pre5aa1 Andrea Arcangeli
2003-03-14 13:53 ` 2.4.21pre5aa1 Rik van Riel
2003-03-14 17:35 ` Andrea Arcangeli [this message]
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=20030314173550.GG1375@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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