[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221115155802.p3vjnk7eqqcyskt3@box.shutemov.name>
Date: Tue, 15 Nov 2022 18:58:02 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Dave Hansen <dave.hansen@...el.com>
Cc: kernel test robot <lkp@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
x86@...nel.org, Dave Hansen <dave.hansen@...ux.intel.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: [tip:x86/mm 5/16] sound/core/hwdep.c:243:24: sparse: sparse:
incorrect type in assignment (different address spaces)
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
Powered by blists - more mailing lists