linux-kernel - Re: building i386 requires s390: "driver/crypto/Kconfig" sourcing s390 arch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <464E3FBD.7090704@oracle.com>
Date:	Fri, 18 May 2007 17:07:25 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	Linda Walsh <lkml@...nx.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: building i386 requires s390: "driver/crypto/Kconfig" sourcing
 s390 arch

Robert P. J. Day wrote:
> 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

I just tried several things to "fix" it, but none of them worked.

I wouldn't mind making missing files in *config be non-fatal, i.e.,
just print a warning message, but I doubt that the maintainer(s)
would accept that.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/