From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, NICE_REPLY_A,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-pl1-f182.google.com (mail-pl1-f182.google.com [209.85.214.182]) by gnuweeb.org (Postfix) with ESMTPS id 78319830F1 for ; Fri, 17 Feb 2023 02:52:28 +0000 (UTC) Authentication-Results: gnuweeb.org; dkim=pass (2048-bit key; unprotected) header.d=kernel-dk.20210112.gappssmtp.com header.i=@kernel-dk.20210112.gappssmtp.com header.a=rsa-sha256 header.s=20210112 header.b=SPcEG6N5; dkim-atps=neutral Received: by mail-pl1-f182.google.com with SMTP id j6so120796plh.1 for ; Thu, 16 Feb 2023 18:52:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; t=1676602348; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=u5iUXheFgWYa0lev5TedkwnVUVIifUqB68alT5VCFtc=; b=SPcEG6N5z4alHKVQ5V2cQm3O4DR6V8EcB2dQrkpaz0+OvnJUAx53erTnZQbdQENu1S l+PvqfHAJWRog6KirSgcWvCSreJmA/kyuTYwjxpHz2QFt7f6nnr6qZ2SZs/BtDPDZhU6 5nG3EJQKwMVi5por1q5q/CtOBZfqtFEKi5YKHkYXXQ4lhAJ0mh6tro8bU7Buj5G7Jtki VS1aKQPZs/c+4IpyEPtzWS+WOyLBbePkebXMqbNZFa0pEwB9pnkuh9ah7ZcKnwexLBhZ uKWtq84yJxtMfSgLhby6I/rtbuLMAXuWhTH15MdxwuQVBar69KBIqLV8TCdmsXEXMwok 3IUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1676602348; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=u5iUXheFgWYa0lev5TedkwnVUVIifUqB68alT5VCFtc=; b=s5KmKR/ZLbBo0AirxRiYbFFYLcibtJPct2kTw6sg1WKqmppFwDVJl+XEoY9leuUkaF ORB3iyeMf7I89dKp+P2KFbkLCRIQqJqlYIK1LGp9LcdUeAr0kJjmxtflw9KKfOIB7Ini xUV497f0k1FJZ6QUZbdCM8oiXHjU3DkLTNGcHZl47IzgALUyyZnlW3oAocdVERgKSst+ uOvYbdqEtpklu7D4MnEmL9iU+GS87mCq5Ol4z8FCHCCtilSzcNMFaeTm7WapvVT1IYWM vXGJtkIozXPVuz4LudVbB8zYoWchQ0Tx7/FnjE6ZUdKZeGIpnWkHSuMqhQ+fH/BrPrwL flVw== X-Gm-Message-State: AO0yUKVLgP/aFmXwRpOHop66YlAJ6VrXI5VySujB3oHAyrDQ7EKiqxaM oQcywUod38xcBJxsdsJ3q8G0Fw== X-Google-Smtp-Source: AK7set925lmZiyZCtA/cFt6vBm9gYn+r7GWJUYb7DXMmpPAdVqQNj/jsH3chAsmAbbwo8Ww6gltiyQ== X-Received: by 2002:a05:6a20:7f8e:b0:bc:604a:5a94 with SMTP id d14-20020a056a207f8e00b000bc604a5a94mr8516170pzj.1.1676602347859; Thu, 16 Feb 2023 18:52:27 -0800 (PST) Received: from [192.168.1.136] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id w2-20020aa78582000000b005a8cc32b23csm764174pfn.20.2023.02.16.18.52.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Feb 2023 18:52:27 -0800 (PST) Message-ID: Date: Thu, 16 Feb 2023 19:52:26 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: [ammarfaizi2-block:axboe/linux-block/for-6.3/block 148/148] block/blk-merge.c:984:42: sparse: sparse: incorrect type in initializer (different base types) Content-Language: en-US To: kernel test robot , Ming Lei Cc: oe-kbuild-all@lists.linux.dev, Ammar Faizi , GNU/Weeb Mailing List References: <202302170743.GXypM9Rt-lkp@intel.com> From: Jens Axboe In-Reply-To: <202302170743.GXypM9Rt-lkp@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: On 2/16/23 4:47?PM, kernel test robot wrote: > sparse warnings: (new ones prefixed by >>) >>> block/blk-merge.c:984:42: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted blk_opf_t const [usertype] ff @@ got unsigned int @@ > block/blk-merge.c:984:42: sparse: expected restricted blk_opf_t const [usertype] ff > block/blk-merge.c:984:42: sparse: got unsigned int > block/blk-merge.c:1010:42: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted blk_opf_t const [usertype] ff @@ got unsigned int @@ > block/blk-merge.c:1010:42: sparse: expected restricted blk_opf_t const [usertype] ff > block/blk-merge.c:1010:42: sparse: got unsigned int >>> block/blk-merge.c:763:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@ > block/blk-merge.c:763:24: sparse: expected unsigned int > block/blk-merge.c:763:24: sparse: got restricted blk_opf_t > block/blk-merge.c:765:28: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@ > block/blk-merge.c:765:28: sparse: expected unsigned int > block/blk-merge.c:765:28: sparse: got restricted blk_opf_t >>> block/blk-merge.c:763:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@ > block/blk-merge.c:763:24: sparse: expected unsigned int > block/blk-merge.c:763:24: sparse: got restricted blk_opf_t > block/blk-merge.c:765:28: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@ > block/blk-merge.c:765:28: sparse: expected unsigned int > block/blk-merge.c:765:28: sparse: got restricted blk_opf_t I fixed this up, thanks for the report. -- Jens Axboe