From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <jdamato@fastly.com>
Cc: netdev@vger.kernel.org, saeedm@nvidia.com, tariqt@nvidia.com,
ecree@solarflare.com, andrew@lunn.ch, kuba@kernel.org,
davem@davemloft.net, leon@kernel.org, pabeni@redhat.com,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [net-next v2 0/2] rxfh with custom RSS fixes
Date: Fri, 28 Jul 2023 09:00:27 +0000 [thread overview]
Message-ID: <169053482796.22021.4158483891713381939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230725205655.310165-1-jdamato@fastly.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 25 Jul 2023 20:56:53 +0000 you wrote:
> Greetings:
>
> Welcome to v2, now via net-next. No functional changes; only style
> changes (see the summary below).
>
> While attempting to get the RX flow hash key for a custom RSS context on
> my mlx5 NIC, I got an error:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: ethtool: Unify ETHTOOL_{G,S}RXFH rxnfc copy
https://git.kernel.org/netdev/net-next/c/801b27e88046
- [net-next,v2,2/2] net/mlx5: Fix flowhash key set/get for custom RSS
https://git.kernel.org/netdev/net-next/c/0212e5d915a2
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:[~2023-07-28 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 20:56 Joe Damato
2023-07-25 20:56 ` [net-next v2 1/2] net: ethtool: Unify ETHTOOL_{G,S}RXFH rxnfc copy Joe Damato
2023-07-25 20:56 ` [net-next v2 2/2] net/mlx5: Fix flowhash key set/get for custom RSS Joe Damato
2023-07-26 8:36 ` Tariq Toukan
2023-07-28 9: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=169053482796.22021.4158483891713381939.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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
Powered by JetHome