From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, xiaoliang.yang_1@nxp.com,
claudiu.manoil@nxp.com, richard.pearn@nxp.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net 1/2] net: enetc: move enetc_set_psfp() out of the common enetc_set_features()
Date: Tue, 20 Sep 2022 19:00:19 +0000 [thread overview]
Message-ID: <166370041967.20640.16151381451398906801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220916133209.3351399-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 16 Sep 2022 16:32:08 +0300 you wrote:
> The VF netdev driver shouldn't respond to changes in the NETIF_F_HW_TC
> flag; only PFs should. Moreover, TSN-specific code should go to
> enetc_qos.c, which should not be included in the VF driver.
>
> Fixes: 79e499829f3f ("net: enetc: add hw tc hw offload features for PSPF capability")
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> [...]
Here is the summary with links:
- [v2,net,1/2] net: enetc: move enetc_set_psfp() out of the common enetc_set_features()
https://git.kernel.org/netdev/net/c/fed38e64d9b9
- [v2,net,2/2] net: enetc: deny offload of tc-based TSN features on VF interfaces
https://git.kernel.org/netdev/net/c/5641c751fe2f
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:[~2022-09-20 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:32 [PATCH v2 net 1/2] net: enetc: move enetc_set_psfp() out of the common enetc_set_features() Vladimir Oltean
2022-09-16 13:32 ` [PATCH v2 net 2/2] net: enetc: deny offload of tc-based TSN features on VF interfaces Vladimir Oltean
2022-09-20 19:00 ` 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=166370041967.20640.16151381451398906801.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richard.pearn@nxp.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.