From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com. [68.232.153.90]) by gmr-mx.google.com with ESMTPS id t138si244527ywc.7.2016.08.19.06.41.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2016 06:41:58 -0700 (PDT) From: "Allen Hubbe" References: <002201d1f1be$a24fe400$e6efac00$@emc.com> <20160818215604.GA19986@mobilestation> <20160819091000.GA14241@mobilestation> In-Reply-To: <20160819091000.GA14241@mobilestation> Subject: RE: [PATCH v2 1/3] ntb: Add asynchronous devices support to NTB-bus interface Date: Fri, 19 Aug 2016 09:41:41 -0400 Message-ID: <000001d1fa1f$6cddf230$4699d690$@emc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Language: en-us To: 'Serge Semin' Cc: jdmason@kudzu.us, dave.jiang@intel.com, Xiangliang.Yu@amd.com, Sergey.Semin@t-platforms.ru, linux-ntb@googlegroups.com, linux-kernel@vger.kernel.org List-ID: From: Serge Semin > 3) IDT driver redevelopment will take a lot of time, since I don't have much free time to > do it. It may be half of year or even more. > > From my side, such an improvement will significantly complicate the NTB Kernel API. Since > you are the subsystem maintainer it's your decision which design to choose, but I don't think > I'll do the IDT driver suitable for this design anytime soon. I'm sorry to have made you feel that way. > > I hope we got it settled now. If not, We can have a Skype conversation, since writing > such a long letters takes lot of time. Come join irc.oftc.net #ntb