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;
Feedback-ID: ie3994620:Fastmail
Date:   Tue, 15 Nov 2022 18:58:02 +0300
From:   "Kirill A. Shutemov" <kirill@shutemov.name>
To:     Dave Hansen <dave.hansen@intel.com>
Cc:     kernel test robot <lkp@intel.com>,
        "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
        oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
        x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
        "James E.J. Bottomley" <jejb@linux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [tip:x86/mm 5/16] sound/core/hwdep.c:243:24: sparse: sparse:
 incorrect type in assignment (different address spaces)
Message-ID: <20221115155802.p3vjnk7eqqcyskt3@box.shutemov.name>
References: <202211150551.T7mpZomP-lkp@intel.com>
 <fdae3de9-db03-b04d-1992-bc8efd053053@intel.com>
 <20221115034007.go64rirsoqazpks7@box.shutemov.name>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221115034007.go64rirsoqazpks7@box.shutemov.name>
Precedence: bulk

On Tue, Nov 15, 2022 at 06:40:07AM +0300, Kirill A. Shutemov wrote:
> I also looked again at get_user() and put_user() and I think we can
> simplify them. The variable just adds noise.

I just realized that this is not only cleanup, but also fixes sparse
warnings.

-- 
  Kiryl Shutsemau / Kirill A. Shutemov