From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch,
Wojciech Drewek <wojciech.drewek@intel.com>,
corbet@lwn.net, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, jesse.brandeburg@intel.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 v2 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values
Date: Mon, 9 Oct 2023 09:37:55 -0700 [thread overview]
Message-ID: <20231009093755.19f9ec9c@kernel.org> (raw)
In-Reply-To: <20231006224726.443836-3-ahmed.zaki@intel.com>
On Fri, 6 Oct 2023 16:47:22 -0600 Ahmed Zaki wrote:
> Fixes: 7bd527aa174f ("ice: Adjust naming for inner VLAN operations")
If there is v3 please drop the Fixes tag.
If the mistake doesn't result in a triggerable bug there's no need
to backport this and therefore no need to annotate the source of
the problem. It will just confuse people into thinking it's a real
issue.
_______________________________________________
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,
linux-doc@vger.kernel.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, Wojciech Drewek <wojciech.drewek@intel.com>
Subject: Re: [PATCH net-next v2 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values
Date: Mon, 9 Oct 2023 09:37:55 -0700 [thread overview]
Message-ID: <20231009093755.19f9ec9c@kernel.org> (raw)
In-Reply-To: <20231006224726.443836-3-ahmed.zaki@intel.com>
On Fri, 6 Oct 2023 16:47:22 -0600 Ahmed Zaki wrote:
> Fixes: 7bd527aa174f ("ice: Adjust naming for inner VLAN operations")
If there is v3 please drop the Fixes tag.
If the mistake doesn't result in a triggerable bug there's no need
to backport this and therefore no need to annotate the source of
the problem. It will just confuse people into thinking it's a real
issue.
next prev parent reply other threads:[~2023-10-09 16:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 22:47 [Intel-wired-lan] [PATCH net-next v2 0/6] Support symmetric RSS (Toeplitz) hash Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 1/6] net: ethtool: allow symmetric RSS hash for any flow type Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-07 0:22 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-07 0:22 ` Jakub Kicinski
2023-10-07 9:01 ` [Intel-wired-lan] " Willem de Bruijn
2023-10-07 9:01 ` Willem de Bruijn
2023-10-10 20:10 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-10 20:10 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-09 16:37 ` Jakub Kicinski [this message]
2023-10-09 16:37 ` Jakub Kicinski
2023-10-10 20:08 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-10 20:08 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 3/6] ice: refactor RSS configuration Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 4/6] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 5/6] ice: enable symmetric RSS Toeplitz hash for any flow type Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 6/6] iavf: enable symmetric RSS Toeplitz hash Ahmed Zaki
2023-10-06 22:47 ` Ahmed Zaki
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=20231009093755.19f9ec9c@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=edumazet@google.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=wojciech.drewek@intel.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.