Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5312567ybl; Tue, 27 Aug 2019 02:42:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqxtScijV4ZjbiCe4smM0QuzN28LvLqdGKP3EO6P9Uwfrf0gquRltHYEOaCG/QpdACVqATZZ X-Received: by 2002:aa7:85d6:: with SMTP id z22mr24268592pfn.262.1566898969450; Tue, 27 Aug 2019 02:42:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566898969; cv=none; d=google.com; s=arc-20160816; b=pQ7Ca2hw1jynxP/DqAB/WWjRGpQzieUxmnGjhERqMacfFYrljaJSKdeXuDj2g3TvBM dMt9maTMoXRurcQ0ojiHMsR08LUfk15t0pHRVWKLfHA2hx+okzOsG5lNc0OdARoN5KqM OXk2tqtbUu3jufwTC1JrsPjyo2KxtfGtKLFtHkndEL/CF2UKh/qKA8KqEo94mvaw+/5K PpMp4X7KzcxFB2ZIAmgfAvAv6FnDeLQnXtNc+OmApVNWpl29N7xJsCYNiMmRsVcErVkx n5XSEFRy1tS5AP7n31XPrkDLkCD1+Y+c1vRCIrUk1vDkPjieMj2owhPjWE/8o/Ft6Lg7 q1hQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=cuH10Pd5aSlwZrdeCk9nr2swR7Cxs3l2fuRvvA/wt04=; b=Umj1/F8BtgkeZ4/SeohExPa3YvHgSjlYld67loykyWkmHiKytWA4z+m/ebXKn5zKid xYR2goC8y9wVYeOzr6y6Th/VIfsqnNB5Y096T3sAhCBdngMfCCwoNz79wQGqOBLkC5/1 r5BaYtepYlrRK95/4i77U49f1cyu5BZjQl9WvaAAIi6U7SEqzQMcUt1DZVY9gP+SJnHx DBYO8Iu/GUn7oSZUzqFLvM2CgjYsCIVeI2IIDO79UxLEGLSFU036W1D0MGjaXoYvZiCL 0Qb9ldZmTv9CXzu/hv3KZ3prUgwBZVv+TFsJFSjB248+IpoXKmMIyRA7QCOElywkgx3x TubA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 142si11216987pgf.35.2019.08.27.02.42.33; Tue, 27 Aug 2019 02:42:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729405AbfH0Jlm (ORCPT + 99 others); Tue, 27 Aug 2019 05:41:42 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:5222 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728806AbfH0Jlm (ORCPT ); Tue, 27 Aug 2019 05:41:42 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id D708052352A06A23A45C; Tue, 27 Aug 2019 17:41:38 +0800 (CST) Received: from [10.177.253.249] (10.177.253.249) by smtp.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.439.0; Tue, 27 Aug 2019 17:41:38 +0800 Subject: Re: [Virtio-fs] [PATCH 04/19] virtio: Implement get_shm_region for PCI transport To: Vivek Goyal References: <20190821175720.25901-1-vgoyal@redhat.com> <20190821175720.25901-5-vgoyal@redhat.com> <5D63392C.3030404@huawei.com> <20190826130607.GB3561@redhat.com> CC: , , , kbuild test robot , , , , "Sebastien Boeuf" From: piaojun Message-ID: <5D64FAD2.2050906@huawei.com> Date: Tue, 27 Aug 2019 17:41:38 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20190826130607.GB3561@redhat.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.253.249] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/8/26 21:06, Vivek Goyal wrote: > On Mon, Aug 26, 2019 at 09:43:08AM +0800, piaojun wrote: > > [..] >>> +static bool vp_get_shm_region(struct virtio_device *vdev, >>> + struct virtio_shm_region *region, u8 id) >>> +{ >>> + struct virtio_pci_device *vp_dev = to_vp_device(vdev); >>> + struct pci_dev *pci_dev = vp_dev->pci_dev; >>> + u8 bar; >>> + u64 offset, len; >>> + phys_addr_t phys_addr; >>> + size_t bar_len; >>> + char *bar_name; >> >> 'char *bar_name' should be cleaned up to avoid compiling warning. And I >> wonder if you mix tab and blankspace for code indent? Or it's just my >> email display problem? > > Will get rid of now unused bar_name. > OK > Generally git flags if there are tab/space issues. I did not see any. So > if you see something, point it out and I will fix it. > cohuck found the same indent problem and pointed them in another email. Jun