netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<christophe.jaillet@wanadoo.fr>, <horms@kernel.org>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH -next] netlink: Use the BITS_PER_LONG macro
Date: Mon, 2 Sep 2024 18:39:44 -0700	[thread overview]
Message-ID: <20240902183944.6779c0a5@kernel.org> (raw)
In-Reply-To: <20240902111052.2686366-1-ruanjinjie@huawei.com>

On Mon, 2 Sep 2024 19:10:52 +0800 Jinjie Ruan wrote:
> sizeof(unsigned long) * 8 is the number of bits in an unsigned long
> variable, replace it with BITS_PER_LONG macro to make it simpler.

Does coccicheck catch such cases?

  reply	other threads:[~2024-09-03  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 11:10 [PATCH -next] netlink: Use the BITS_PER_LONG macro Jinjie Ruan
2024-09-03  1:39 ` Jakub Kicinski [this message]
2024-09-03  2:06   ` Jinjie Ruan
2024-09-03 16:12     ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240902183944.6779c0a5@kernel.org \
    --to=kuba@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ruanjinjie@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).