linux-kernel - Re: Kconfig variable "COBALT" is not defined anywhere

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: <20070603132309.508738b7.randy.dunlap@oracle.com>
Date:	Sun, 3 Jun 2007 13:23:09 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Kconfig variable "COBALT" is not defined anywhere

On Sun, 3 Jun 2007 13:17:48 -0400 (EDT) Robert P. J. Day wrote:

> 
>   (no one's listed as the official cobalt maintainer so i thought i'd
> just throw this out there.)
> 
>   there is no Kconfig file which defines the selectable option
> "COBALT", which means that this snippet from drivers/char/nvram.c:
> 
> #  if defined(CONFIG_COBALT)
> #    include <linux/cobalt-nvram.h>
> #    define MACH COBALT
> #  else
> #    define MACH PC
> #  endif
> 
> never evaluates to true, therefore making <linux/cobalt-nvram.h>
> fairly useless, at least under the circumstances.

Maybe it should be MIPS_COBALT ?


---
~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/