From: patchwork-bot+netdevbpf@kernel.org
To: Corinna Vinschen <vinschen@redhat.com>
Cc: netdev@vger.kernel.org, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
kuba@kernel.org
Subject: Re: [PATCH v2 net-next] net: stmmac: propagate feature flags to vlan
Date: Wed, 19 Apr 2023 04:50:18 +0000 [thread overview]
Message-ID: <168187981802.31004.10264768603245180857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230417192845.590034-1-vinschen@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 17 Apr 2023 21:28:45 +0200 you wrote:
> stmmac_dev_probe doesn't propagate feature flags to VLANs. So features
> like offloading don't correspond with the general features and it's not
> possible to manipulate features via ethtool -K to affect VLANs.
>
> Propagate feature flags to vlan features. Drop TSO feature because
> it does not work on VLANs yet.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: stmmac: propagate feature flags to vlan
https://git.kernel.org/netdev/net-next/c/6b2c6e4a938f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-04-19 4:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 13:00 [PATCH net-next] net: stmmac: propagate feature flags to vlan Corinna Vinschen
2023-04-11 15:44 ` Simon Horman
2023-04-11 22:36 ` Jacob Keller
2023-04-12 13:11 ` Corinna Vinschen
2023-04-12 14:45 ` Jakub Kicinski
2023-04-12 14:50 ` Corinna Vinschen
2023-04-13 4:15 ` Jakub Kicinski
2023-04-13 15:25 ` Corinna Vinschen
2023-04-13 16:00 ` Jakub Kicinski
2023-04-17 19:03 ` Corinna Vinschen
2023-04-17 19:11 ` Jakub Kicinski
2023-04-17 19:28 ` [PATCH v2 " Corinna Vinschen
2023-04-19 4:50 ` patchwork-bot+netdevbpf [this message]
2023-06-22 8:20 ` [PATCH " Oleksij Rempel
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=168187981802.31004.10264768603245180857.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=vinschen@redhat.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).