linux-kernel - Re: linux-next: boot failure in sep driver

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] [day] [month] [year] [list]

Message-Id: <20101125103550.7d30b643.sfr@canb.auug.org.au>
Date:	Thu, 25 Nov 2010 10:35:50 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	sedat.dilek@...il.com
Cc:	Sedat Dilek <sedat.dilek@...glemail.com>,
	LKML <linux-kernel@...r.kernel.org>, mark.a.allyn@...el.com,
	jayant.mangalampalli@...el.com, Greg KH <gregkh@...e.de>,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: linux-next: boot failure in sep driver

On Tue, 23 Nov 2010 15:49:57 +0100 Sedat Dilek
<sedat.dilek@...glemail.com> wrote:
>
> just fall into the same pitfall... While digging into this driver, I
> saw a typo in:
> 
> [ drivers/staging/sep/Kconfig ]
> 
> config DX_SEP
>         tristate "Discretix SEP driver"
>         depends on PCI
>         default y
          ^^^^^^^^^
Of course, this is not helping ... as Linus says "Your driver is not that
important".

>         help
>           Discretix SEP driver; used for the security processor subsystem
>           on bard the Intel Mobile Internet Device.
> 
>           The driver's name is sep_driver.
> 
>           If unsure, select N.

It even suggests not selecting it ...

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped