From: Nikolay Aleksandrov <razor@blackwall.org>
To: Ted Chen <znscnchen@gmail.com>, roopa@nvidia.com
Cc: bridge@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] bridge: Make br_is_nd_neigh_msg() accept pointer to "const struct sk_buff"
Date: Sat, 4 Jan 2025 11:35:49 +0200 [thread overview]
Message-ID: <5237f91a-bfbb-41c5-acd8-03ac26052e50@blackwall.org> (raw)
In-Reply-To: <20250104083846.71612-1-znscnchen@gmail.com>
On 1/4/25 10:38, Ted Chen wrote:
> The skb_buff struct in br_is_nd_neigh_msg() is never modified. Mark it as
> const.
>
> Signed-off-by: Ted Chen <znscnchen@gmail.com>
> ---
> v2:
> - Rebased to net-next (Nicolay)
> - Wrapped commit message lines to be within 75 characters. (Nicolay)
> - Added net-next to patch subject. (Nicolay)
>
> v1:
> https://lore.kernel.org/all/20250103070900.70014-1-znscnchen@gmail.com
> ---
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2025-01-04 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 8:38 [PATCH net-next v2] bridge: Make br_is_nd_neigh_msg() accept pointer to "const struct sk_buff" Ted Chen
2025-01-04 9:35 ` Nikolay Aleksandrov [this message]
2025-01-07 14:20 ` 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=5237f91a-bfbb-41c5-acd8-03ac26052e50@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
--cc=znscnchen@gmail.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