From: Sudeep Dutt <sudeep.dutt@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sudeep Dutt <sudeep.dutt@intel.com>,
"Woodruff, Robert J" <robert.j.woodruff@intel.com>,
james harvey <jamespharvey20@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Nikhil Rao <nikhil.rao@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: rdma-core doesn't install driver.h, broke libibscif
Date: Thu, 18 Oct 2018 08:10:00 -0700 [thread overview]
Message-ID: <1539875400.18931.450.camel@localhost> (raw)
In-Reply-To: <20181017085453.GA30496@infradead.org>
On Wed, 2018-10-17 at 01:54 -0700, Christoph Hellwig wrote:
> On Mon, Oct 15, 2018 at 05:53:44PM +0000, Woodruff, Robert J wrote:
> > James Harvey wrote,
> >
> > >Short: Is libibscif dead, and should OS repositories remove it?
> >
> > Libibscif is for an old product, Intel's KNC, that is no longer sold and the S/W is frozen. The open source libibscif is no longer maintained.
> > It has already been removed from the latest community OFED distribution. The individual package on the OFA downloads is for archive purposed only.
>
> Does this mean we can kill the kernel scif code as well?
The MIC COSM drivers are using the kernel SCIF code. These drivers have
been upstream since 2015 and we are not sure who is using them. Our
preference will be to keep these drivers in the kernel for now.
Thanks,
Sudeep Dutt
prev parent reply other threads:[~2018-10-18 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9C6B67F36DCAFC479B1CF6A967258A8CAB401945@ORSMSX115.amr.corp.intel.com>
2018-10-17 8:54 ` rdma-core doesn't install driver.h, broke libibscif Christoph Hellwig
2018-10-18 15:10 ` Sudeep Dutt [this message]
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=1539875400.18931.450.camel@localhost \
--to=sudeep.dutt@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jamespharvey20@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=robert.j.woodruff@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;
as well as URLs for NNTP newsgroup(s).