[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <188ea71f265a4f9c968de68dc9ea6464@AcuMS.aculab.com>
Date: Mon, 21 Mar 2022 09:04:46 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Dan Carpenter' <dan.carpenter@...cle.com>,
Martin Kaiser <martin@...ser.cx>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Larry Finger <Larry.Finger@...inger.net>,
Phillip Potter <phil@...lpotter.co.uk>,
"Michael Straube" <straube.linux@...il.com>,
"linux-staging@...ts.linux.dev" <linux-staging@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] staging: r8188eu: remove local BIT macro
From: Dan Carpenter
> Sent: 21 March 2022 08:16
>
> This version is better, thanks!
>
> Reviewed-by: Dan Carpenter <dan.carpenter@...cle.com>
>
> What the GCC devs should have done is run their checker on real code and
> silence the common false positives. There are a few ways to do this.
> You could make ~ a special case. They already ignore truncated sign
> extension so they could equally well ignore truncation when all it's a
> 32 bits which are all set to 1. Probably the best answer is to do both.
Or start using -(BIT_VALUE + 1) instead of ~BIT_VALUE :-)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists