From: Valdis.Kletnieks@vt.edu
To: Oren Weil <oren.jer.weil@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
alan@linux.intel.com, david@woodhou.se
Subject: Re: [PATCH 7/7] char/mei: Updates to char/Kconfig ane char/Makefile
Date: Wed, 23 Mar 2011 17:43:27 -0400 [thread overview]
Message-ID: <29997.1300916607@localhost> (raw)
In-Reply-To: Your message of "Tue, 22 Mar 2011 12:51:32 +0200." <1300791092-14319-8-git-send-email-oren.jer.weil@intel.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Tue, 22 Mar 2011 12:51:32 +0200, Oren Weil said:
> Changes of Kconfig and Makefile in driver/char
> for adding the Intel MEI Driver to the Linux kernel.
> New Makefile building for MEI Driver.
> +config INTEL_MEI
> + tristate "Intel Management Engine Interface (Intel MEI)"
> + depends on X86 && EXPERIMENTAL
> + help
> + The Intel Management Engine (Intel ME) provides Manageability,
> + Security and Media services for system containing Intel chipsets.
> + if selected /dev/mei misc device will be created.
Can we have this re-worded so it doesn't have an implied "all Intel chipsets",
perhaps adding "chipsets that support the Intel vPro technology", or similar?
(And though I found that at least *some* vPro-capable chipsets do IME, I didn't
find a statement that *all* vPro will do it, so I'm still confused, thus no
patch from me...)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-03-23 21:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 10:51 [PATCH 0/7] char/mei: Intel MEI Driver Oren Weil
2011-03-22 10:51 ` [PATCH 1/7] char/mei: PCI device and char driver support Oren Weil
2011-03-22 17:22 ` Arnd Bergmann
2011-03-22 21:57 ` Alan Cox
2011-03-22 22:22 ` Greg KH
2011-03-22 23:04 ` Alan Cox
2011-03-23 7:59 ` Arnd Bergmann
2011-03-22 10:51 ` [PATCH 2/7] char/mei: Interrupt handling Oren Weil
2011-03-22 10:51 ` [PATCH 3/7] char/mei: MEI "Link" layer code - MEI Hardware communications Oren Weil
2011-03-22 10:51 ` [PATCH 4/7] char/mei: MEI driver init flow Oren Weil
2011-03-22 10:51 ` [PATCH 5/7] char/mei: Hardware and MEI driver internal struct definition Oren Weil
2011-03-22 10:51 ` [PATCH 6/7] char/mei: Header file contain the Userland API, (IOCTL and its struct) Oren Weil
2011-03-22 16:26 ` Greg KH
2011-03-22 16:41 ` Arnd Bergmann
2011-03-22 10:51 ` [PATCH 7/7] char/mei: Updates to char/Kconfig ane char/Makefile Oren Weil
2011-03-23 21:43 ` Valdis.Kletnieks [this message]
2011-03-22 16:23 ` [PATCH 0/7] char/mei: Intel MEI Driver Greg KH
2011-03-23 12:25 ` Weil, Oren jer
2011-03-23 13:50 ` Greg KH
2011-03-22 16:50 ` Arnd Bergmann
2011-03-23 7:20 ` Weil, Oren jer
2011-03-23 13:51 ` Greg KH
2011-03-23 15:55 ` Weil, Oren jer
2011-03-23 16:06 ` Greg KH
2011-03-23 16:20 ` Arnd Bergmann
2011-03-24 12:54 ` Weil, Oren jer
2011-03-24 13:10 ` Arnd Bergmann
2011-04-04 15:54 ` Pavel Machek
2011-04-05 6:01 ` Weil, Oren jer
2011-04-18 13:53 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29997.1300916607@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=alan@linux.intel.com \
--cc=david@woodhou.se \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oren.jer.weil@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.