[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b48f1ae32ba49f38dcfe11f912c4ace@AcuMS.aculab.com>
Date: Thu, 4 Nov 2021 09:17:07 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Eric Dumazet' <eric.dumazet@...il.com>,
Leonard Crestez <cdleonard@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
David Ahern <dsahern@...nel.org>
CC: Dmitry Safonov <0x7f454c46@...il.com>,
Kuniyuki Iwashima <kuniyu@...zon.co.jp>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
"Jakub Kicinski" <kuba@...nel.org>,
Neal Cardwell <ncardwell@...gle.com>,
"Yuchung Cheng" <ycheng@...gle.com>,
Enke Chen <enchen@...oaltonetworks.com>,
Wei Wang <weiwan@...gle.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] tcp: Use BIT() for OPTION_* constants
From: Eric Dumazet
> Sent: 03 November 2021 22:50
>
> On 11/3/21 3:17 PM, Leonard Crestez wrote:
> > Extending these flags using the existing (1 << x) pattern triggers
> > complaints from checkpatch. Instead of ignoring checkpatch modify the
> > existing values to use BIT(x) style in a separate commit.
> >
> > Signed-off-by: Leonard Crestez <cdleonard@...il.com>
> >
>
> Yes, I guess checkpatch does not know that we currently use at most 16 bits :)
>
> u16 options = opts->options;
>
> Anyway, this seems fine.
Doesn't BIT() have a nasty habit of generating 64bit constants
that just cause a different set of issues when inverted?
It may be safe here - but who knows.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists