[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241008151934.58f124f1@kernel.org>
Date: Tue, 8 Oct 2024 15:19:34 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: netdev@...r.kernel.org, mkarsten@...terloo.ca, skhawaja@...gle.com,
sdf@...ichev.me, bjorn@...osinc.com, amritha.nambiar@...el.com,
sridhar.samudrala@...el.com, willemdebruijn.kernel@...il.com, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Donald Hunter <donald.hunter@...il.com>, Jesper
Dangaard Brouer <hawk@...nel.org>, Mina Almasry <almasrymina@...gle.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Daniel Jurgens
<danielj@...dia.com>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC net-next v4 6/9] netdev-genl: Support setting per-NAPI
config values
On Tue, 8 Oct 2024 11:20:47 -0700 Joe Damato wrote:
> Noticed this while re-reading the code; planning on changing this
> from NLA_S32 to NLA_U32 for v5.
Make sure you edit the spec, not the output. Looks like there may be
a problem here (napi-id vs id in the attributes).
Make sure you run: ./tools/net/ynl/ynl-regen.sh -f
and the tree is clean afterwards
Powered by blists - more mailing lists