Message-ID: <60796c88-eae1-3ae0-019d-73b49c9d4c1e@linux.alibaba.com> Date: Tue, 14 Dec 2021 23:51:10 +0800 MIME-Version: 1.0 References: <20211102055646.103337-1-jefflexu@linux.alibaba.com> <7815cbb4-4889-4d37-14d1-a23a0a960204@linux.alibaba.com> From: JeffleXu In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Virtio-fs] [PATCH v7 0/6] virtiofsd: support per inode DAX List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Miklos Szeredi , Vivek Goyal Cc: virtio-fs-list , Joseph Qi On 12/14/21 6:17 PM, Miklos Szeredi wrote: > On Mon, 13 Dec 2021 at 19:03, Vivek Goyal wrote: >> >> On Fri, Dec 10, 2021 at 10:54:20AM +0800, JeffleXu wrote: >>> Hi Vivek, >>> >>> Besides, I'd like to know that, to make the per inode DAX feature merged >>> into v5.17, shall the patches for virtiofsd also be ready during the >>> merge window? >> >> I think having virtiofsd patches ready is not a strict requirement to >> merge kernel patches. I will provide my ack for the kernel patches. >> After that it is up to the Miklos to accept or reject those patches. > > Pushed to fuse.git#for-next. > > The user API needed porting, the userspace part will have to take that > into account. The only other change I did was replace the !! > construct with a (bool) cast. Hi, what do you mean by 'The user API needed porting'? Do you mean this patch set for virtiofsd? -- Thanks, Jeffle