Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp3728769pxb; Fri, 4 Feb 2022 15:15:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJz+GdDmXnY6gCc4UHCW5A96vnEvNaS1Cr1286UoQhxWJk2cVFouhqZtv4vcY+Y7ymmLoq1y X-Received: by 2002:a62:5383:: with SMTP id h125mr5347079pfb.30.1644016536185; Fri, 04 Feb 2022 15:15:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644016536; cv=none; d=google.com; s=arc-20160816; b=c0j3L4a3e6/EyRNUV5/eQerMRu9PrstsFID4pcHNh3HTaVv8eWYahTHwnTclkDmL9a OiiTYhrtV/gTsuwqqBhqAtNdvtyYOrz9XyASZcR7M9yHnKmB6h6b8lhFiFzTTB2wD20Z oFGJ08kNE/+v7u5fiVdLhRIweasOUZ88/7EJzsHk5hHIUxDYiMiM4fZM7a0HqbG2bwT0 BzECKMiGNPt9wKbdO+8YgSi7zOdx4+Et6BZFUQDGP5gaaDUskvZJEzcNPtP0pVbZ5kSU ukP9zMF2okFg7e/GmRiNf6Bn7658HKfPtdpjpwNgXn8tqVEOcoseWIT2oe8ihW+FbCds owkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=OZf1ROxpD9B4TWcyHIn3jjg4uM8+1EYb7mlM8BqEVV8=; b=SZjQr6sA1OSe6tZohuJwaLpF4RdwWKrEocfgJQxNxmrQgq06X0le/YRdGW+dBH0/x0 Ggtr9yAKzm04drPSXsN770VUToEH/ofxgIwoT3RKj6Eb+DKDAN60ie0sPSXw0Ls/kmX6 hhZfyqH27Ls0H+nTBeJ+Q25FNf2T3jCUmnt9SoHyO94e7Edq0Bv/9LpFlQ2crMoCnGET MVx2+hkWCEn5bpz8R67Jf13tZT07t0oecvnZc+4zzC61wvTKxV7hwe8tZQfAuG0JoNKY 36Ib3hX4T59D6aQ8kCfdTDmO4vf+0+PzEgL5VU//Cu7HSLSisbQ1LbVJDhMrvgKKEjCa 8law== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FvfTNXyr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w71si3101121pgd.43.2022.02.04.15.15.24; Fri, 04 Feb 2022 15:15:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FvfTNXyr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349082AbiBCCkx (ORCPT + 99 others); Wed, 2 Feb 2022 21:40:53 -0500 Received: from mga06.intel.com ([134.134.136.31]:10743 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231602AbiBCCkm (ORCPT ); Wed, 2 Feb 2022 21:40:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643856042; x=1675392042; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=GIjjktIkiLNrP/r1mZS+FYVdRHq8JPEaPLAA76V2CRE=; b=FvfTNXyrzG78WT3Q2xwMS6PBk4VcGyhromJK5OUCTrI++W+wClfxKrmO XTHIu7DErF+o5WeJScmcHEmRuDUvVWAt37JfEgWb6F7eQB82JLdvWUEPu l/Z7majcmSuIbfzc9ULnw+rS+UPOOTFra/qfVuOZgPSnp7OtlFCyjXXuF 3iVGyWM1LvVoQ8WH6gcONKvnkl9VRRLl5MTroUJ+8DKlsoZDwJrVb4TQj Y9TB6bPPiDcnB5It/1PgGNfg4MCetjEab6JEHXXzXb70bTeU3wzSoKeUw Khzat9j7qB3Fk8SXUV82YjSlBSTq8HFuIcV+1aSZyuJIRTzeKQomv8Mhg g==; X-IronPort-AV: E=McAfee;i="6200,9189,10246"; a="308792903" X-IronPort-AV: E=Sophos;i="5.88,338,1635231600"; d="scan'208";a="308792903" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Feb 2022 18:40:42 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,338,1635231600"; d="scan'208";a="627290208" Received: from lkp-server01.sh.intel.com (HELO 276f1b88eecb) ([10.239.97.150]) by fmsmga002.fm.intel.com with ESMTP; 02 Feb 2022 18:40:39 -0800 Received: from kbuild by 276f1b88eecb with local (Exim 4.92) (envelope-from ) id 1nFS34-000VS3-Cq; Thu, 03 Feb 2022 02:40:38 +0000 Date: Thu, 3 Feb 2022 10:39:45 +0800 From: kernel test robot To: Jorgen Hansen , linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org Cc: kbuild-all@lists.01.org, gregkh@linuxfoundation.org, pv-drivers@vmware.com, Jorgen Hansen , Vishnu Dasa Subject: Re: [PATCH 7/8] VMCI: dma dg: add support for DMA datagrams sends Message-ID: <202202031004.SmRs3Z6M-lkp@intel.com> References: <20220202144910.10349-8-jhansen@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220202144910.10349-8-jhansen@vmware.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jorgen, I love your patch! Perhaps something to improve: [auto build test WARNING on char-misc/char-misc-testing] [also build test WARNING on linux/master linus/master v5.17-rc2 next-20220202] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Jorgen-Hansen/VMCI-dma-dg-Add-support-for-DMA-datagrams/20220202-230034 base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git 7ab004dbcbee38b8a70798835d3ffcd97a985a5e config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220203/202202031004.SmRs3Z6M-lkp@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce: # apt-get install sparse # sparse version: v0.6.4-dirty # https://github.com/0day-ci/linux/commit/303777a2a8daa11d529827395318bb698ddee57e git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Jorgen-Hansen/VMCI-dma-dg-Add-support-for-DMA-datagrams/20220202-230034 git checkout 303777a2a8daa11d529827395318bb698ddee57e # save the config file to linux build tree mkdir build_dir make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/misc/vmw_vmci/ If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot sparse warnings: (new ones prefixed by >>) drivers/misc/vmw_vmci/vmci_guest.c:106:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *addr @@ got char * @@ drivers/misc/vmw_vmci/vmci_guest.c:106:45: sparse: expected void const volatile [noderef] __iomem *addr drivers/misc/vmw_vmci/vmci_guest.c:106:45: sparse: got char * drivers/misc/vmw_vmci/vmci_guest.c:103:14: sparse: sparse: symbol 'vmci_read_reg' was not declared. Should it be static? drivers/misc/vmw_vmci/vmci_guest.c:113:44: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got char * @@ drivers/misc/vmw_vmci/vmci_guest.c:113:44: sparse: expected void volatile [noderef] __iomem *addr drivers/misc/vmw_vmci/vmci_guest.c:113:44: sparse: got char * drivers/misc/vmw_vmci/vmci_guest.c:110:6: sparse: sparse: symbol 'vmci_write_reg' was not declared. Should it be static? >> drivers/misc/vmw_vmci/vmci_guest.c:118:5: sparse: sparse: symbol 'vmci_write_data' was not declared. Should it be static? drivers/misc/vmw_vmci/vmci_guest.c:554:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected char *mmio_base @@ got void [noderef] __iomem * @@ drivers/misc/vmw_vmci/vmci_guest.c:554:27: sparse: expected char *mmio_base drivers/misc/vmw_vmci/vmci_guest.c:554:27: sparse: got void [noderef] __iomem * drivers/misc/vmw_vmci/vmci_guest.c:909:43: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void [noderef] __iomem * @@ got char *mmio_base @@ drivers/misc/vmw_vmci/vmci_guest.c:909:43: sparse: expected void [noderef] __iomem * drivers/misc/vmw_vmci/vmci_guest.c:909:43: sparse: got char *mmio_base Please review and possibly fold the followup patch. --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org