Re: [PATCH char-misc-next v4 00/13] misc: mic: SCIF driver

[Greg Kroah-Hartman]

On Tue, Apr 28, 2015 at 01:45:12PM -0700, Sudeep Dutt wrote:
> On Mon, 2015-03-30 at 18:36 -0700, Sudeep Dutt wrote:
> > ChangeLog:
> > =========
> > 
> > v3 => v4:
> > a) Delete unused IOCTL definitions and IOCTL interface fixes as per
> > feedback from Greg Kroah-Hartman
> > b) Couple of tiny bug fixes since v3
> > 
> > v2 => v3 @ https://lkml.org/lkml/2015/1/26/849
> > a) Formatting fixes for SCIF header file documentation, data type fixes
> >    for SCIF IOCTL interface and added SCIF user space documentation in
> >    scif_overview.txt as per feedback from Greg Kroah-Hartman
> > 
> > v1 => v2 @ https://lkml.org/lkml/2015/1/12/1029
> > a) Use kernel-doc formatting for SCIF header file documentation, enhance
> >    SCIF ring buffer documentation and formatting cleanup in patch 4 as
> >    per feedback from Greg Kroah-Hartman
> > b) SCIF bug fixes and cleanups since initial post
> > 
> > v1: Initial post @ https://lkml.org/lkml/2014/12/10/546
> > 
> > Description:
> > ============
> > 
> > The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a low
> > level communications API across PCIe currently implemented for MIC. Currently
> > SCIF provides inter-node communication within a single host platform, where a
> > node is a MIC Coprocessor or Xeon based host. SCIF abstracts the details of
> > communicating over the PCIe bus while providing an API that is symmetric
> > across all the nodes in the PCIe network. An important design objective for SCIF
> > is to deliver the maximum possible performance given the communication
> > abilities of the hardware. SCIF has been used to implement an offload compiler
> > runtime and OFED support for MPI implementations for MIC coprocessors.
> > 
> 
> Hi Greg,
> 
> Please take a look at this patch series.

What patch series?  I don't have this in my todo queue at all, what
happened to it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/