From: Paul Bolle <pebolle@tiscali.nl>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [PATCH char-misc-next v4 08/13] misc: mic: SCIF open close bind and listen APIs
Date: Tue, 31 Mar 2015 10:39:12 +0200 [thread overview]
Message-ID: <1427791152.2408.53.camel@x220> (raw)
In-Reply-To: <78c7ec12b16153ce91c23bb0f20b46eaf38b78f2.1427763968.git.sudeep.dutt@intel.com>
On Mon, 2015-03-30 at 18:36 -0700, Sudeep Dutt wrote:
> --- a/drivers/misc/mic/Kconfig
> +++ b/drivers/misc/mic/Kconfig
> +comment "SCIF Driver"
> +
> +config SCIF
> + tristate "SCIF Driver"
> + depends on 64BIT && PCI && X86 && SCIF_BUS
Won't this work with just
depends on SCIF_BUS
> + help
> + This enables SCIF Driver support for the Intel Many Integrated
> + Core (MIC) family of PCIe form factor coprocessor devices that
> + run a 64 bit Linux OS. The Symmetric Communication Interface
> + (SCIF (pronounced as skiff)) is a low level communications API
> + across PCIe currently implemented for MIC.
> +
> + If you are building a host kernel with an Intel MIC device then
> + say M (recommended) or Y, else say N. If unsure say N.
> +
> + More information about the Intel MIC family as well as the Linux
> + OS and tools for MIC to use with this driver are available from
> + <http://software.intel.com/en-us/mic-developer>.
Paul Bolle
next prev parent reply other threads:[~2015-03-31 8:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 1:36 [PATCH char-misc-next v4 00/13] misc: mic: SCIF driver Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 01/13] misc: mic: SCIF header file and IOCTL interface Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 02/13] misc: mic: SCIF ring buffer infrastructure Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 03/13] misc: mic: SCIF Hardware Bus Sudeep Dutt
2015-03-31 8:36 ` Paul Bolle
2015-03-31 1:36 ` [PATCH char-misc-next v4 04/13] misc: mic: SCIF Peer Bus Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 05/13] misc: mic: Common MIC header file changes in preparation for SCIF Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 06/13] misc: mic: SCIF module initialization Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 07/13] misc: mic: SCIF node queue pair setup management Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 08/13] misc: mic: SCIF open close bind and listen APIs Sudeep Dutt
2015-03-31 8:39 ` Paul Bolle [this message]
2015-03-31 21:13 ` Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 09/13] misc: mic: SCIF connections APIs i.e. accept and connect Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 10/13] misc: mic: SCIF messaging and node enumeration APIs Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 11/13] misc: mic: MIC host driver specific changes to enable SCIF Sudeep Dutt
2015-03-31 8:42 ` Paul Bolle
2015-03-31 1:36 ` [PATCH char-misc-next v4 12/13] misc: mic: MIC card " Sudeep Dutt
2015-03-31 1:36 ` [PATCH char-misc-next v4 13/13] misc: mic: add support for loading/unloading SCIF driver Sudeep Dutt
2015-04-28 20:45 ` [PATCH char-misc-next v4 00/13] misc: mic: " Sudeep Dutt
2015-04-29 11:27 ` Greg Kroah-Hartman
2015-04-29 12:42 ` Sudeep Dutt
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=1427791152.2408.53.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=sudeep.dutt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox