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 C1249CCA480 for ; Mon, 20 Jun 2022 19:21:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1343589AbiFTTVU (ORCPT ); Mon, 20 Jun 2022 15:21:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343617AbiFTTVR (ORCPT ); Mon, 20 Jun 2022 15:21:17 -0400 Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7DC8E1C109; Mon, 20 Jun 2022 12:21:16 -0700 (PDT) Received: by mail-ed1-x52d.google.com with SMTP id eo8so16512211edb.0; Mon, 20 Jun 2022 12:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/0jxbATVEDKJnIt6ABi4UcKvefavHfALqV2faNdj1xk=; b=E2w9SsK622uI3mRxf9d1ClkzeccxGN5eH53Unw5M4E4b0/ciI8EdJTKHuIfMDb3oYJ YTDXeesnCEDlZdX1+VVgBVcyrcc1kjQhXUl7QhujJt1ZGMR2a7e0T1PcupO4HUGZdiFD 39IpbFP7Xi0rCmSlptLDWbdMNNlf9hIPR48cNLSNpAavFS7XyQE1FOIVXFDngH7HEOLz EtQ6srucKJaxyDr+flGCni5+E4AlE5K+pYwH7NKtnjDBeQN4QNkmdg+EOpiVfF9aJDQD P0cQv8kp38qvfnww9Mbzg40KkFzsj1eem1AjDaHXAaN8ujWQnF1PUAt6Vyo1EdmDOpUI J49A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/0jxbATVEDKJnIt6ABi4UcKvefavHfALqV2faNdj1xk=; b=KS1ZbQe1BDe0RhVhVm2Ez74LCKPlGvUARPcMA5AHV6pUM1V70Y20T2EDL81ea3fvD4 dN6Or7bYI+c/0Z0hgNobwhjzk4JH/flGXUA5b6UZJv9YosbgJPZxFszVmNEgSqDTvZGg PKfi29lCbSZJ/10voH5dh43hf6fJPO2GtdP06IDR20BSwDF5GkOKFQ7A/U/UXcm0gymL cJ4w1+7ObeFt4o5DTA3TuFKyQA6jDN3B9w8MR5mJqKjPfb7i40YeVf1F4/bpjGNJsIxN fCFaX6HCQss8f7gJJ6kayUCzvosSEqw/pysU3oGM6AGkHoDPlELPauUnSOZ9jkCWbP59 UOww== X-Gm-Message-State: AJIora+hRb69bcBVdThzUWyuddXTz7thEbwScGLQtubWuq8/p7ug9vZG QW0gdKy5HgPyFHDtxL6kgYg= X-Google-Smtp-Source: AGRyM1s7UDK4xMx70oMoQG8mkudNnGwBUAoUHsgJQ7yqWiUaYK2qbi0m7Q+0UFQ5sVxeWk33gHpWbA== X-Received: by 2002:a05:6402:5418:b0:435:5a48:daa9 with SMTP id ev24-20020a056402541800b004355a48daa9mr25144978edb.304.1655752874902; Mon, 20 Jun 2022 12:21:14 -0700 (PDT) Received: from mail (239.125-180-91.adsl-dyn.isp.belgacom.be. [91.180.125.239]) by smtp.gmail.com with ESMTPSA id f23-20020a170906825700b0070ad296e4b0sm6388168ejx.186.2022.06.20.12.21.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Jun 2022 12:21:14 -0700 (PDT) Date: Mon, 20 Jun 2022 21:21:12 +0200 From: Luc Van Oostenryck To: Alexander Lobakin Cc: Arnd Bergmann , Yury Norov , Andy Shevchenko , Mark Rutland , Matt Turner , Brian Cain , Geert Uytterhoeven , Yoshinori Sato , Rich Felker , "David S. Miller" , Kees Cook , "Peter Zijlstra (Intel)" , Marco Elver , Borislav Petkov , Tony Luck , Maciej Fijalkowski , Jesse Brandeburg , Greg Kroah-Hartman , linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, kbuild-all@lists.01.org, kernel test robot Subject: Re: [alobakin:bitops 3/7] block/elevator.c:222:9: sparse: sparse: cast from restricted req_flags_t Message-ID: <20220620192112.ghyegqvtj3ud7zla@mail> References: <202206191726.wq70mbMK-lkp@intel.com> <20220617144031.2549432-1-alexandr.lobakin@intel.com> <20220620135146.2628908-1-alexandr.lobakin@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220620135146.2628908-1-alexandr.lobakin@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-sh@vger.kernel.org On Mon, Jun 20, 2022 at 03:51:46PM +0200, Alexander Lobakin wrote: > From: kernel test robot > Date: Sun, 19 Jun 2022 17:20:05 +0800 > > Also, could someone please help me with this? I don't get what went > wrong with sparse, it's not even some new code, just moving old > stuff. Hi, The first sparse's warnings (sparse: preprocessor token __ATOMIC_*) are already fixed (and most probably, the bots have already taken the fix). I'm working on the second ones (sparse: unreplaced symbol). -- Luc (Sparse's maintainer) From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2159775042906933752==" MIME-Version: 1.0 From: Luc Van Oostenryck To: kbuild-all@lists.01.org Subject: Re: [alobakin:bitops 3/7] block/elevator.c:222:9: sparse: sparse: cast from restricted req_flags_t Date: Mon, 20 Jun 2022 21:21:12 +0200 Message-ID: <20220620192112.ghyegqvtj3ud7zla@mail> In-Reply-To: <20220620135146.2628908-1-alexandr.lobakin@intel.com> List-Id: --===============2159775042906933752== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Mon, Jun 20, 2022 at 03:51:46PM +0200, Alexander Lobakin wrote: > From: kernel test robot > Date: Sun, 19 Jun 2022 17:20:05 +0800 > = > Also, could someone please help me with this? I don't get what went > wrong with sparse, it's not even some new code, just moving old > stuff. Hi, The first sparse's warnings (sparse: preprocessor token __ATOMIC_*) are alr= eady fixed (and most probably, the bots have already taken the fix). I'm working on the second ones (sparse: unreplaced symbol). -- Luc (Sparse's maintainer) --===============2159775042906933752==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Date: Mon, 20 Jun 2022 19:21:12 +0000 Subject: Re: [alobakin:bitops 3/7] block/elevator.c:222:9: sparse: sparse: cast from restricted req_flags_t Message-Id: <20220620192112.ghyegqvtj3ud7zla@mail> List-Id: References: <202206191726.wq70mbMK-lkp@intel.com> <20220617144031.2549432-1-alexandr.lobakin@intel.com> <20220620135146.2628908-1-alexandr.lobakin@intel.com> In-Reply-To: <20220620135146.2628908-1-alexandr.lobakin@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alexander Lobakin Cc: Arnd Bergmann , Yury Norov , Andy Shevchenko , Mark Rutland , Matt Turner , Brian Cain , Geert Uytterhoeven , Yoshinori Sato , Rich Felker , "David S. Miller" , Kees Cook , "Peter Zijlstra (Intel)" , Marco Elver , Borislav Petkov , Tony Luck , Maciej Fijalkowski , Jesse Brandeburg , Greg Kroah-Hartman , linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, kbuild-all@lists.01.org, kernel test robot On Mon, Jun 20, 2022 at 03:51:46PM +0200, Alexander Lobakin wrote: > From: kernel test robot > Date: Sun, 19 Jun 2022 17:20:05 +0800 > > Also, could someone please help me with this? I don't get what went > wrong with sparse, it's not even some new code, just moving old > stuff. Hi, The first sparse's warnings (sparse: preprocessor token __ATOMIC_*) are already fixed (and most probably, the bots have already taken the fix). I'm working on the second ones (sparse: unreplaced symbol). -- Luc (Sparse's maintainer) From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luc Van Oostenryck Subject: Re: [alobakin:bitops 3/7] block/elevator.c:222:9: sparse: sparse: cast from restricted req_flags_t Date: Mon, 20 Jun 2022 21:21:12 +0200 Message-ID: <20220620192112.ghyegqvtj3ud7zla@mail> References: <202206191726.wq70mbMK-lkp@intel.com> <20220617144031.2549432-1-alexandr.lobakin@intel.com> <20220620135146.2628908-1-alexandr.lobakin@intel.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/0jxbATVEDKJnIt6ABi4UcKvefavHfALqV2faNdj1xk=; b=E2w9SsK622uI3mRxf9d1ClkzeccxGN5eH53Unw5M4E4b0/ciI8EdJTKHuIfMDb3oYJ YTDXeesnCEDlZdX1+VVgBVcyrcc1kjQhXUl7QhujJt1ZGMR2a7e0T1PcupO4HUGZdiFD 39IpbFP7Xi0rCmSlptLDWbdMNNlf9hIPR48cNLSNpAavFS7XyQE1FOIVXFDngH7HEOLz EtQ6srucKJaxyDr+flGCni5+E4AlE5K+pYwH7NKtnjDBeQN4QNkmdg+EOpiVfF9aJDQD P0cQv8kp38qvfnww9Mbzg40KkFzsj1eem1AjDaHXAaN8ujWQnF1PUAt6Vyo1EdmDOpUI J49A== Content-Disposition: inline In-Reply-To: <20220620135146.2628908-1-alexandr.lobakin@intel.com> List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alexander Lobakin Cc: Arnd Bergmann , Yury Norov , Andy Shevchenko , Mark Rutland , Matt Turner , Brian Cain , Geert Uytterhoeven , Yoshinori Sato , Rich Felker , "David S. Miller" , Kees Cook , "Peter Zijlstra (Intel)" , Marco Elver , Borislav Petkov , Tony Luck , Maciej Fijalkowski , Jesse Brandeburg , Greg Kroah-Hartman , linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org On Mon, Jun 20, 2022 at 03:51:46PM +0200, Alexander Lobakin wrote: > From: kernel test robot > Date: Sun, 19 Jun 2022 17:20:05 +0800 > > Also, could someone please help me with this? I don't get what went > wrong with sparse, it's not even some new code, just moving old > stuff. Hi, The first sparse's warnings (sparse: preprocessor token __ATOMIC_*) are already fixed (and most probably, the bots have already taken the fix). I'm working on the second ones (sparse: unreplaced symbol). -- Luc (Sparse's maintainer)