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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9BC36C19F2D for ; Tue, 9 Aug 2022 10:23:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231355AbiHIKX2 (ORCPT ); Tue, 9 Aug 2022 06:23:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232615AbiHIKXZ (ORCPT ); Tue, 9 Aug 2022 06:23:25 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 50B3918360 for ; Tue, 9 Aug 2022 03:23:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1660040605; x=1691576605; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=EPYnAUfjYb96gXY6+8JJ3sFiLBxcSud8g/qim46UvP8=; b=MDDyp1WpAY0rzcWIW6Ktt8rEQ7Wx8uw78pF2TCTR7aLnz7YR+O/FZcZF LEGBewfKhvuyhErrYy3e3agjXzdUw/xdeC9N0EIg/8XWYx7bEkdSd80Ee /eH2mn3CxzYV8qEyrHYSeQbfw1diR64yfkqvxM9ptH08FJeXMQOdOzGez M5zwWcZFzt7lLVz3sU6Evxa5PwjpdKvjBUtkik+jgLWYQ+53OUzqRHZYl 6yaj8WSOqdac/b+q9XFcUnCxvhoaZLnKzUIS2sD3e130ghoRL7fYNSDnA a3eECiikbs956ZPSKQPqj4A5eN9VeNnaKCWdZvGfo92F00AV2CqwKlMra Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10433"; a="316731060" X-IronPort-AV: E=Sophos;i="5.93,224,1654585200"; d="scan'208";a="316731060" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Aug 2022 03:23:24 -0700 X-IronPort-AV: E=Sophos;i="5.93,224,1654585200"; d="scan'208";a="633278227" Received: from rongch2-mobl.ccr.corp.intel.com (HELO [10.254.208.171]) ([10.254.208.171]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Aug 2022 03:23:23 -0700 Subject: Re: [kbuild-all] Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types) To: Bart Van Assche , kernel test robot Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, Jens Axboe References: <202208061258.jAwlaAXe-lkp@intel.com> From: "Chen, Rong A" Message-ID: Date: Tue, 9 Aug 2022 18:23:21 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/6/2022 11:21 PM, Bart Van Assche wrote: > On 8/5/22 21:44, kernel test robot wrote: >>     drivers/md/raid10.c:1139:30: sparse: sparse: incorrect type in >> initializer (different base types) @@     expected int const op @@ >> got restricted blk_opf_t enum req_op @@ >>     drivers/md/raid10.c:1139:30: sparse:     expected int const op >>     drivers/md/raid10.c:1139:30: sparse:     got restricted blk_opf_t >> enum req_op >>     drivers/md/raid10.c:1140:52: sparse: sparse: incorrect type in >> initializer (different base types) @@     expected unsigned long const >> do_sync @@     got restricted blk_opf_t @@ >>     drivers/md/raid10.c:1140:52: sparse:     expected unsigned long >> const do_sync >>     drivers/md/raid10.c:1140:52: sparse:     got restricted blk_opf_t > > I can't reproduce this with Linus' master branch. It seems like the > kernel test robot picked a commit somewhere halfway my patch series? > > Bart. Hi Bart, Only the warning prefixed by '>>' is related to this commit 4ce4c73f662b: >> drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types) @@ expected restricted blk_opf_t [usertype] opf @@ got int rw @@ and I can reproduce it in my system. Best Regards, Rong Chen