Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752044AbcDOX2G (ORCPT ); Fri, 15 Apr 2016 19:28:06 -0400 Received: from mga11.intel.com ([192.55.52.93]:22860 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751491AbcDOX2D (ORCPT ); Fri, 15 Apr 2016 19:28:03 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,489,1455004800"; d="scan'208";a="946216109" Date: Fri, 15 Apr 2016 19:28:01 -0400 From: Ira Weiny To: Leon Romanovsky Cc: Christoph Hellwig , Jason Gunthorpe , Dennis Dalessandro , dledford@redhat.com, linux-rdma@vger.kernel.org, linux-fsdevel@vger.kernel.org, torvalds@linux-foundation.org, viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/7] IB/hfi1: Remove write() and use ioctl() for user access Message-ID: <20160415232800.GA32513@rhel> References: <20160414153727.6387.96381.stgit@scvm10.sc.intel.com> <20160414164550.GC6247@obsidianresearch.com> <20160414174830.GA11641@rhel.sc.intel.com> <20160415040126.GB10689@leon.nu> <20160415161754.GA21549@rhel> <20160415173035.GC10689@leon.nu> <20160415173401.GA10868@infradead.org> <20160415212328.GF10689@leon.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160415212328.GF10689@leon.nu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 555 Lines: 18 On Sat, Apr 16, 2016 at 12:23:28AM +0300, Leon Romanovsky wrote: > > Intel as usual decided to do it in their way and the result is presented > on this mailing list. Excuse me, but this statement is completely unfair. We were specifically asked by Al and Linus to fix our char device with regards to the write/writev inconsistency. https://www.spinics.net/lists/linux-rdma/msg34451.html Which is _exactly_ what this patch series does. Do you have a technical reason that this patch series does not fix the write/writev issue brought up by Al? Ira