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

Message-ID: <AANLkTin6ZJr3vXw=HVeA65aq39qxtnJGGXW2nwfp_PwS@mail.gmail.com>
Date:	Tue, 23 Nov 2010 15:49:57 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	LKML <linux-kernel@...r.kernel.org>, mark.a.allyn@...el.com,
	jayant.mangalampalli@...el.com
Cc:	sfr@...b.auug.org.au, Greg KH <gregkh@...e.de>,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: linux-next: boot failure in sep driver

Hi,

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
        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.
- EOF -

Shouldn't this be "...used for the security processor subsystem...
"...*shipped with Intel Mobile Internet Devices.*" ?
I can only imagine that the original author(s) wanted to figure out it
is an onboard-solution.


Kind Regards,
- Sedat -

P.S.: Note to myself: Add the folowing snippet to:

[ debian/config/config ]
...
##
## file: drivers/staging/sep/Kconfig
##
# CONFIG_DX_SEP is not set
...
--
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/