From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch,
willemdebruijn.kernel@gmail.com, corbet@lwn.net,
netdev@vger.kernel.org, gal@nvidia.com,
linux-doc@vger.kernel.org, jesse.brandeburg@intel.com,
ecree.xilinx@gmail.com, edumazet@google.com,
anthony.l.nguyen@intel.com, horms@kernel.org,
vladimir.oltean@nxp.com, intel-wired-lan@lists.osuosl.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v7 0/8] Support symmetric-xor RSS hash
Date: Wed, 6 Dec 2023 09:55:40 -0800 [thread overview]
Message-ID: <20231206095540.5df7c5a5@kernel.org> (raw)
In-Reply-To: <20231205230049.18872-1-ahmed.zaki@intel.com>
On Tue, 5 Dec 2023 16:00:41 -0700 Ahmed Zaki wrote:
> Patches 1 and 2 modify the get/set_rxh ethtool API to take a pointer to
> struct of parameters instead of individual params. This will allow future
> changes to the uAPI-shared struct ethtool_rxfh without changing the
> drivers' API.
Looks like it breaks the allmodconfig build.
--
pw-bot: cr
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
corbet@lwn.net, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, vladimir.oltean@nxp.com,
andrew@lunn.ch, horms@kernel.org, mkubecek@suse.cz,
willemdebruijn.kernel@gmail.com, gal@nvidia.com,
alexander.duyck@gmail.com, ecree.xilinx@gmail.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/8] Support symmetric-xor RSS hash
Date: Wed, 6 Dec 2023 09:55:40 -0800 [thread overview]
Message-ID: <20231206095540.5df7c5a5@kernel.org> (raw)
In-Reply-To: <20231205230049.18872-1-ahmed.zaki@intel.com>
On Tue, 5 Dec 2023 16:00:41 -0700 Ahmed Zaki wrote:
> Patches 1 and 2 modify the get/set_rxh ethtool API to take a pointer to
> struct of parameters instead of individual params. This will allow future
> changes to the uAPI-shared struct ethtool_rxfh without changing the
> drivers' API.
Looks like it breaks the allmodconfig build.
--
pw-bot: cr
next prev parent reply other threads:[~2023-12-06 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 23:00 [Intel-wired-lan] [PATCH net-next v7 0/8] Support symmetric-xor RSS hash Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 1/8] net: ethtool: pass a pointer to parameters to get/set_rxfh ethtool ops Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-06 12:57 ` [Intel-wired-lan] " Alexander Lobakin
2023-12-06 12:57 ` Alexander Lobakin
2023-12-06 13:03 ` Ahmed Zaki
2023-12-06 13:03 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 2/8] net: ethtool: get rid of get/set_rxfh_context functions Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 3/8] net: ethtool: add support for symmetric-xor RSS hash Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 4/8] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 5/8] ice: refactor RSS configuration Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 6/8] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 7/8] ice: enable symmetric-xor RSS for Toeplitz hash function Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-05 23:00 ` [Intel-wired-lan] [PATCH net-next v7 8/8] iavf: " Ahmed Zaki
2023-12-05 23:00 ` Ahmed Zaki
2023-12-06 17:55 ` Jakub Kicinski [this message]
2023-12-06 17:55 ` [PATCH net-next v7 0/8] Support symmetric-xor RSS hash Jakub Kicinski
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=20231206095540.5df7c5a5@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=willemdebruijn.kernel@gmail.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.