From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A94DC74A21 for ; Wed, 10 Jul 2019 14:27:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 58E1D20651 for ; Wed, 10 Jul 2019 14:27:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727927AbfGJO1S (ORCPT ); Wed, 10 Jul 2019 10:27:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57998 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727154AbfGJO1R (ORCPT ); Wed, 10 Jul 2019 10:27:17 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 868C9307CDFC; Wed, 10 Jul 2019 14:27:17 +0000 (UTC) Received: from dhcp201-121.englab.pnq.redhat.com (ovpn-116-55.sin2.redhat.com [10.67.116.55]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6EA411711D; Wed, 10 Jul 2019 14:27:06 +0000 (UTC) From: Pankaj Gupta To: virtualization@lists.linux-foundation.org, dan.j.williams@intel.com Cc: yuval.shaia@oracle.com, linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org, cohuck@redhat.com, mst@redhat.com, lcapitulino@redhat.com, pagupta@redhat.com Subject: [PATCH] virtio_pmem: fix sparse warning Date: Wed, 10 Jul 2019 19:57:00 +0530 Message-Id: <20190710142700.10215-1-pagupta@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Wed, 10 Jul 2019 14:27:17 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch fixes below sparse warning related to __virtio type in virtio pmem driver. This is reported by Intel test bot on linux-next tree. nd_virtio.c:56:28: warning: incorrect type in assignment (different base types) nd_virtio.c:56:28: expected unsigned int [unsigned] [usertype] type nd_virtio.c:56:28: got restricted __virtio32 nd_virtio.c:93:59: warning: incorrect type in argument 2 (different base types) nd_virtio.c:93:59: expected restricted __virtio32 [usertype] val nd_virtio.c:93:59: got unsigned int [unsigned] [usertype] ret Signed-off-by: Pankaj Gupta Reported-by: kbuild test robot --- This fixes a warning, so submitting it as a separate patch on top of virtio pmem series. include/uapi/linux/virtio_pmem.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/uapi/linux/virtio_pmem.h b/include/uapi/linux/virtio_pmem.h index efcd72f2d20d..f89129bf1f84 100644 --- a/include/uapi/linux/virtio_pmem.h +++ b/include/uapi/linux/virtio_pmem.h @@ -23,12 +23,12 @@ struct virtio_pmem_config { struct virtio_pmem_resp { /* Host return status corresponding to flush request */ - __u32 ret; + __virtio32 ret; }; struct virtio_pmem_req { /* command type */ - __u32 type; + __virtio32 type; }; #endif -- 2.20.1