All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	sridhar.samudrala@intel.com, aleksandr.loktionov@intel.com,
	aleksander.lobakin@intel.com, dinesh.kumar@intel.com,
	anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, almasrymina@google.com,
	willemb@google.com, pmenzel@molgen.mpg.de
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 1/3] virtchnl2: rename enum virtchnl2_cap_rss
Date: Fri, 16 May 2025 09:54:16 +0100	[thread overview]
Message-ID: <20250516085416.GC1898636@horms.kernel.org> (raw)
In-Reply-To: <20250423192705.1648119-2-ahmed.zaki@intel.com>

On Wed, Apr 23, 2025 at 01:27:03PM -0600, Ahmed Zaki wrote:
> The "enum virtchnl2_cap_rss" will be used for negotiating flow
> steering capabilities. Instead of adding a new enum, rename
> virtchnl2_cap_rss to virtchnl2_flow_types. Also rename the enum's
> constants.
> 
> Flow steering will use this enum in the next patches.
> 
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>

Reviewed-by: Simon Horman <horms@kernel.org>


WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	sridhar.samudrala@intel.com, aleksandr.loktionov@intel.com,
	aleksander.lobakin@intel.com, dinesh.kumar@intel.com,
	anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, almasrymina@google.com,
	willemb@google.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH iwl-next v5 1/3] virtchnl2: rename enum virtchnl2_cap_rss
Date: Fri, 16 May 2025 09:54:16 +0100	[thread overview]
Message-ID: <20250516085416.GC1898636@horms.kernel.org> (raw)
In-Reply-To: <20250423192705.1648119-2-ahmed.zaki@intel.com>

On Wed, Apr 23, 2025 at 01:27:03PM -0600, Ahmed Zaki wrote:
> The "enum virtchnl2_cap_rss" will be used for negotiating flow
> steering capabilities. Instead of adding a new enum, rename
> virtchnl2_cap_rss to virtchnl2_flow_types. Also rename the enum's
> constants.
> 
> Flow steering will use this enum in the next patches.
> 
> Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2025-05-16  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 19:27 [Intel-wired-lan] [PATCH iwl-next v5 0/3] idpf: add flow steering support Ahmed Zaki
2025-04-23 19:27 ` Ahmed Zaki
2025-04-23 19:27 ` [Intel-wired-lan] [PATCH iwl-next v5 1/3] virtchnl2: rename enum virtchnl2_cap_rss Ahmed Zaki
2025-04-23 19:27   ` Ahmed Zaki
2025-05-16  8:54   ` Simon Horman [this message]
2025-05-16  8:54     ` Simon Horman
2025-04-23 19:27 ` [Intel-wired-lan] [PATCH iwl-next v5 2/3] virtchnl2: add flow steering support Ahmed Zaki
2025-04-23 19:27   ` Ahmed Zaki
2025-05-16  8:54   ` [Intel-wired-lan] " Simon Horman
2025-05-16  8:54     ` Simon Horman
2025-04-23 19:27 ` [Intel-wired-lan] [PATCH iwl-next v5 3/3] idpf: " Ahmed Zaki
2025-04-23 19:27   ` Ahmed Zaki
2025-05-16  8:54   ` [Intel-wired-lan] " Simon Horman
2025-05-16  8:54     ` Simon Horman

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=20250516085416.GC1898636@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=ahmed.zaki@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=dinesh.kumar@intel.com \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=willemb@google.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.