linux-kernel - Re: [RFC PATCH 01/13] Intel(R) MEI 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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 10 Feb 2011 08:50:15 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Oren Weil <oren.jer.weil@...el.com>
Cc:	gregkh@...e.de, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, david@...dhou.se,
	david.woodhouse@...el.com
Subject: Re: [RFC PATCH 01/13] Intel(R) MEI Driver

On 10 Feb 2011 01:54:57 -0800 Oren Weil wrote:

> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> index b7980a8..0a54b26 100644
> --- a/drivers/char/Kconfig
> +++ b/drivers/char/Kconfig
> @@ -1144,5 +1144,16 @@ config RAMOOPS
>  	  This enables panic and oops messages to be logged to a circular
>  	  buffer in RAM where it can be read back at some later point.
>  
> +config INTEL_MEI
> +	tristate "Intel(R) Management Engine Interface (Intel(R) MEI)"
> +	default m

Please don't enable random kconfig options.

> +	depends on EXPERIMENTAL && X86
> +	help
> +	  If you have an Intel(R) ME chip in your system 
> +	  say Yes to enable the Intel(R) Managment Engine interface.
> +	  for more informaiton see
> +	  <http://software.intel.com/en-us/manageability/>
> +
> +
>  endmenu

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