From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Linda Walsh <lkml@tlinx.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: building i386 requires s390: "driver/crypto/Kconfig" sourcing s390 arch
Date: Fri, 18 May 2007 19:32:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705181931180.7794@localhost.localdomain> (raw)
In-Reply-To: <20070518161920.ae0ed062.randy.dunlap@oracle.com>
On Fri, 18 May 2007, Randy Dunlap wrote:
> On Fri, 18 May 2007 14:46:02 -0700 Linda Walsh wrote:
> > If the standard that other architectures are using is to put their
> > devices in the crypto directory, then one might expect all crypto
> > devices to be there. Why should s390 stick out and put its crypto
> > device someplace under the s390 tree, forcing parts of the s390
> > tree to be included when building other architectures?
>
> drivers/crypto/ currently contains drivers for x86_32 and s390 (the
> latter by indirection, which is what is causing you this
> grief/problem/whatever), but it certainly looks like it could be a
> home for crypto drivers on any arch.
this all sounds vaguely familiar. oh, wait ...
http://lkml.org/lkml/2007/3/28/212
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-18 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 19:32 Linda Walsh
2007-05-18 21:17 ` Randy Dunlap
2007-05-18 21:46 ` Linda Walsh
2007-05-18 23:19 ` Randy Dunlap
2007-05-18 23:32 ` Robert P. J. Day [this message]
2007-05-19 0:07 ` Randy Dunlap
2007-05-19 5:38 ` Sam Ravnborg
2007-05-19 6:47 ` Linda Walsh
2007-05-20 10:01 ` Heiko Carstens
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=Pine.LNX.4.64.0705181931180.7794@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=randy.dunlap@oracle.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
all inboxes | Powered by JetHome®