Re: Smatch and sparse errors

On 04/14/2018 03:18 AM, Jasmin J. wrote: > Hello Mauro/Hans! > >> There is already an upstream patch for hidding it: > The patch from https://patchwork.kernel.org/patch/10334353 will not > apply at the smatch tree. > > Attached is an updated version for smatch. > > Even with the patched tools,

Re: Smatch and sparse errors

Em Sat, 14 Apr 2018 12:06:34 +0200 "Jasmin J." escreveu: > Hello Mauro/Hans! > > > Then you're probably not using the right version > Might be ... > The build script from Hans uses the Versions from here: >git://repo.or.cz/smatch.git That's right. The last patch on this

Re: Smatch and sparse errors

Hello Mauro/Hans! > Then you're probably not using the right version Might be ... The build script from Hans uses the Versions from here: git://repo.or.cz/smatch.git git://git.kernel.org/pub/scm/devel/sparse/sparse.git > Yesterday, I added both trees I'm using here at: >

Re: Smatch and sparse errors

Em Sat, 14 Apr 2018 03:18:20 +0200 "Jasmin J." escreveu: > Hello Mauro/Hans! > > > There is already an upstream patch for hidding it: > The patch from https://patchwork.kernel.org/patch/10334353 will not > apply at the smatch tree. > > Attached is an updated version for

Re: Smatch and sparse errors

Hello Mauro/Hans! > There is already an upstream patch for hidding it: The patch from https://patchwork.kernel.org/patch/10334353 will not apply at the smatch tree. Attached is an updated version for smatch. Even with the patched tools, sparse still complains: CC

Smatch and sparse errors

Hi Hans/Jasmin, There is a regression with sparse and upstream Kernels, with also affect smatch. Due to that, both will produce hundreds of new errors on all places that directly or indirectly use min() or max(). Those were caused by those upstream patches: 3c8ba0d61d04 ("kernel.h: