From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org,
xuanzhuo@linux.alibaba.com, andrew@lunn.ch,
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 v5 0/5] netdev_features: start cleaning netdev_features_t up
Date: Tue, 03 Sep 2024 10:40:32 +0000 [thread overview]
Message-ID: <172536003201.249713.3183163361305744893.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240829123340.789395-1-aleksander.lobakin@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 29 Aug 2024 14:33:35 +0200 you wrote:
> NETDEV_FEATURE_COUNT is currently 64, which means we can't add any new
> features as netdev_features_t is u64.
> As per several discussions, instead of converting netdev_features_t to
> a bitmap, which would mean A LOT of changes, we can try cleaning up
> netdev feature bits.
> There's a bunch of bits which don't really mean features, rather device
> attributes/properties that can't be changed via Ethtool in any of the
> drivers. Such attributes can be moved to netdev private flags without
> losing any functionality.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/5] netdevice: convert private flags > BIT(31) to bitfields
(no matching commit)
- [net-next,v5,2/5] netdev_features: convert NETIF_F_LLTX to dev->lltx
(no matching commit)
- [net-next,v5,3/5] netdev_features: convert NETIF_F_NETNS_LOCAL to dev->netns_local
(no matching commit)
- [net-next,v5,4/5] netdev_features: convert NETIF_F_FCOE_MTU to dev->fcoe_mtu
(no matching commit)
- [net-next,v5,5/5] netdev_features: remove NETIF_F_ALL_FCOE
https://git.kernel.org/netdev/net-next/c/a61fec1c87be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-09-03 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:33 [PATCH net-next v5 0/5] netdev_features: start cleaning netdev_features_t up Alexander Lobakin
2024-08-29 12:33 ` [PATCH net-next v5 1/5] netdevice: convert private flags > BIT(31) to bitfields Alexander Lobakin
2024-08-29 12:33 ` [PATCH net-next v5 2/5] netdev_features: convert NETIF_F_LLTX to dev->lltx Alexander Lobakin
2024-08-29 12:33 ` [PATCH net-next v5 3/5] netdev_features: convert NETIF_F_NETNS_LOCAL to dev->netns_local Alexander Lobakin
2024-08-29 12:33 ` [PATCH net-next v5 4/5] netdev_features: convert NETIF_F_FCOE_MTU to dev->fcoe_mtu Alexander Lobakin
2024-09-03 9:55 ` Paolo Abeni
2024-09-04 6:17 ` Martin K. Petersen
2024-08-29 12:33 ` [PATCH net-next v5 5/5] netdev_features: remove NETIF_F_ALL_FCOE Alexander Lobakin
2024-09-03 9:24 ` [PATCH net-next v5 0/5] netdev_features: start cleaning netdev_features_t up Paolo Abeni
2024-09-03 10:40 ` patchwork-bot+netdevbpf [this message]
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=172536003201.249713.3183163361305744893.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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