From: Nikolay Aleksandrov <razor@blackwall.org>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
j.vosburgh@gmail.com, andy@greyhouse.net, dsahern@kernel.org,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
vinicius.gomes@intel.com, johannes@sipsolutions.net,
idosch@nvidia.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH net-next] netlink: make range pointers in policies const
Date: Wed, 25 Oct 2023 22:12:13 +0300 [thread overview]
Message-ID: <1d484f6a-669b-e222-391b-43e3b4904097@blackwall.org> (raw)
In-Reply-To: <20231025162204.132528-1-kuba@kernel.org>
On 10/25/23 19:22, Jakub Kicinski wrote:
> struct nla_policy is usually constant itself, but unless
> we make the ranges inside constant we won't be able to
> make range structs const. The ranges are not modified
> by the core.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: j.vosburgh@gmail.com
> CC: andy@greyhouse.net
> CC: dsahern@kernel.org
> CC: jhs@mojatatu.com
> CC: xiyou.wangcong@gmail.com
> CC: jiri@resnulli.us
> CC: vinicius.gomes@intel.com
> CC: johannes@sipsolutions.net
> CC: razor@blackwall.org
> CC: idosch@nvidia.com
> CC: linux-wireless@vger.kernel.org
> ---
> drivers/net/bonding/bond_netlink.c | 2 +-
> drivers/net/vxlan/vxlan_mdb.c | 2 +-
> include/net/netlink.h | 4 ++--
> net/ipv6/ioam6_iptunnel.c | 2 +-
> net/sched/sch_fq.c | 2 +-
> net/sched/sch_fq_pie.c | 2 +-
> net/sched/sch_qfq.c | 2 +-
> net/sched/sch_taprio.c | 2 +-
> net/wireless/nl80211.c | 2 +-
> tools/net/ynl/ynl-gen-c.py | 2 +-
> 10 files changed, 11 insertions(+), 11 deletions(-)
>
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2023-10-25 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 16:22 [PATCH net-next] netlink: make range pointers in policies const Jakub Kicinski
2023-10-25 16:23 ` Johannes Berg
2023-10-25 18:41 ` David Ahern
2023-10-25 19:12 ` Nikolay Aleksandrov [this message]
2023-10-26 5:44 ` Jiri Pirko
2023-10-26 23:40 ` 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=1d484f6a-669b-e222-391b-43e3b4904097@blackwall.org \
--to=razor@blackwall.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=j.vosburgh@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).