[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e869d690-939a-a5a5-1a8c-fe4b550b69ab@gmail.com>
Date: Wed, 3 Nov 2021 15:49:52 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: 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,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tcp: Use BIT() for OPTION_* constants
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.
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists