From: Gur Stavi <gur.stavi@huawei.com>
To: Gur Stavi <gur.stavi@huawei.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: [PATCH net-next v1 0/1] queue_api: reduce risk of name collision over txq
Date: Sun, 18 May 2025 13:00:53 +0300 [thread overview]
Message-ID: <cover.1747559621.git.gur.stavi@huawei.com> (raw)
Rename local variable in macros from txq to _txq.
When macro parameter get_desc is expended it is likely to have a txq
token that refers to a different txq variable at the caller's site.
Gur Stavi (1):
queue_api: reduce risk of name collision over txq
include/net/netdev_queues.h | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
base-commit: 67fa756408a5359941bea2c021740da5e9ed490d
--
2.45.2
next reply other threads:[~2025-05-18 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 10:00 Gur Stavi [this message]
2025-05-18 10:00 ` [PATCH net-next v1 1/1] queue_api: reduce risk of name collision over txq Gur Stavi
2025-05-19 23:09 ` Jakub Kicinski
2025-05-20 3:20 ` [PATCH net-next v1 0/1] " patchwork-bot+netdevbpf
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=cover.1747559621.git.gur.stavi@huawei.com \
--to=gur.stavi@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).