From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PATCH 2.4.23-pre6 add kmap_types.h for CONFIG_CRYPTO
Date: Fri, 17 Oct 2003 13:32:19 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106639760009691@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106633278923482@msgid-missing>
>>>>> "Matthew" = Matthew Wilcox <willy@debian.org> writes:
Matthew> On Thu, Oct 16, 2003 at 12:29:58PM -0700, Grant Grundler
Matthew> wrote:
>> This doesn't feel like a great solution. Willy suggested the right
>> fix might be to not require all arches to provide asm/kmap_types.h.
>> I'll let the folks who know WTH kmap_types.h is really for debate
>> and submit this with the hope of getting the ia64-linux to build
>> with CONFIG_CRYPTO.
Matthew> Cloning kmap_types from i386 is a pretty bad idea since that
Matthew> architecture actually supports highmem. Better to clone from
Matthew> an arch which has no support for highmem such as ARM.
I'd argue we should fix the crypto code instead, it doesn't seem
reasonable for them to require kmap types to be defined on archs that
don't have highmem.
Cheers,
Jes
next prev parent reply other threads:[~2003-10-17 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 19:29 PATCH 2.4.23-pre6 add kmap_types.h for CONFIG_CRYPTO Grant Grundler
2003-10-16 19:40 ` Matthew Wilcox
2003-10-16 20:23 ` Grant Grundler
2003-10-16 23:20 ` Keith Owens
2003-10-17 12:13 ` Christoph Hellwig
2003-10-17 13:32 ` Jes Sorensen [this message]
2003-10-17 13:33 ` Jes Sorensen
2003-10-23 17:01 ` Bjorn Helgaas
2003-10-23 21:04 ` Keith Owens
2003-10-23 22:15 ` Bjorn Helgaas
2003-10-23 22:28 ` Keith Owens
2003-10-24 18:24 ` Bjorn Helgaas
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=marc-linux-ia64-106639760009691@msgid-missing \
--to=jes@wildopensource.com \
--cc=linux-ia64@vger.kernel.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