From: Jakub Kicinski <kuba@kernel.org>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@kernel.org>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Andrew Lunn <andrew@lunn.ch>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/6] netdevice: convert private flags > BIT(31) to bitfields
Date: Fri, 9 Aug 2024 22:27:55 -0700 [thread overview]
Message-ID: <20240809222755.28acd840@kernel.org> (raw)
In-Reply-To: <20240808152757.2016725-2-aleksander.lobakin@intel.com>
On Thu, 8 Aug 2024 17:27:52 +0200 Alexander Lobakin wrote:
> + * @priv_flags_fast: both hotpath private flags as bits and as bitfield
> + * booleans combined, only to assert cacheline placement
> + * @priv_flags: flags invisible to userspace defined as bits, see
> + * enum netdev_priv_flags for the definitions
The kdoc scripts says:
include/linux/netdevice.h:2392: warning: Excess struct member 'priv_flags_fast' description in 'net_device'
I thought you sent a kernel-doc patch during previous cycle to fix this,
or was that for something else?
next prev parent reply other threads:[~2024-08-10 5:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 15:27 [PATCH net-next v3 0/6] netdev_features: start cleaning netdev_features_t up Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 1/6] netdevice: convert private flags > BIT(31) to bitfields Alexander Lobakin
2024-08-10 5:27 ` Jakub Kicinski [this message]
2024-08-12 12:09 ` Alexander Lobakin
2024-08-12 18:04 ` Jakub Kicinski
2024-08-13 11:53 ` Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 2/6] netdev_features: remove unused __UNUSED_NETIF_F_1 Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 3/6] netdev_features: convert NETIF_F_LLTX to dev->lltx Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 4/6] netdev_features: convert NETIF_F_NETNS_LOCAL to dev->netns_local Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 5/6] netdev_features: convert NETIF_F_FCOE_MTU to dev->fcoe_mtu Alexander Lobakin
2024-08-08 15:27 ` [PATCH net-next v3 6/6] net: netdev_features: remove NETIF_F_ALL_FCOE Alexander Lobakin
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=20240809222755.28acd840@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.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).