From: Larysa Zaremba <larysa.zaremba@intel.com>
To: intel-wired-lan@lists.osuosl.org,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: aleksander.lobakin@intel.com, sridhar.samudrala@intel.com,
"Singhai, Anjali" <anjali.singhai@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Larysa Zaremba <larysa.zaremba@intel.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
Emil Tantilov <emil.s.tantilov@intel.com>,
Madhu Chittim <madhu.chittim@intel.com>,
Josh Hay <joshua.a.hay@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
jayaprakash.shanmugam@intel.com, natalia.wochtman@intel.com,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Richard Cochran <richardcochran@gmail.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH iwl-next v5 02/15] virtchnl: introduce control plane version fields
Date: Mon, 17 Nov 2025 14:48:42 +0100 [thread overview]
Message-ID: <20251117134912.18566-3-larysa.zaremba@intel.com> (raw)
In-Reply-To: <20251117134912.18566-1-larysa.zaremba@intel.com>
From: Victor Raj <victor.raj@intel.com>
In the virtchnl header file, add the Control Plane software version fields.
Signed-off-by: Victor Raj <victor.raj@intel.com>
Reviewed-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
Signed-off-by: Larysa Zaremba <larysa.zaremba@intel.com>
---
include/linux/intel/virtchnl2.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/linux/intel/virtchnl2.h b/include/linux/intel/virtchnl2.h
index 02ae447cc24a..7b0821732ff3 100644
--- a/include/linux/intel/virtchnl2.h
+++ b/include/linux/intel/virtchnl2.h
@@ -505,7 +505,8 @@ VIRTCHNL2_CHECK_STRUCT_LEN(8, virtchnl2_version_info);
* sent per transmit packet without needing to be
* linearized.
* @pad: Padding.
- * @reserved: Reserved.
+ * @cp_ver_major: Control Plane major version number.
+ * @cp_ver_minor: Control Plane minor version number.
* @device_type: See enum virtchl2_device_type.
* @min_sso_packet_len: Min packet length supported by device for single
* segment offload.
@@ -556,7 +557,8 @@ struct virtchnl2_get_capabilities {
__le16 max_tx_hdr_size;
u8 max_sg_bufs_per_tx_pkt;
u8 pad[3];
- u8 reserved[4];
+ __le16 cp_ver_major;
+ __le16 cp_ver_minor;
__le32 device_type;
u8 min_sso_packet_len;
u8 max_hdr_buf_per_lso;
--
2.47.0
next prev parent reply other threads:[~2025-11-17 13:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 13:48 [PATCH iwl-next v5 00/15] Introduce iXD driver Larysa Zaremba
2025-11-17 13:48 ` [PATCH iwl-next v5 01/15] virtchnl: create 'include/linux/intel' and move necessary header files Larysa Zaremba
2026-02-24 17:49 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` Larysa Zaremba [this message]
2025-11-17 13:48 ` [PATCH iwl-next v5 03/15] libie: add PCI device initialization helpers to libie Larysa Zaremba
2026-02-24 7:20 ` [Intel-wired-lan] " R, Bharath
2026-02-24 17:17 ` Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 04/15] libeth: allow to create fill queues without NAPI Larysa Zaremba
2026-02-24 7:17 ` [Intel-wired-lan] " R, Bharath
2026-02-24 17:17 ` Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 05/15] libie: add control queue support Larysa Zaremba
2026-02-24 7:15 ` [Intel-wired-lan] " R, Bharath
2026-02-24 17:17 ` Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 06/15] libie: add bookkeeping support for control queue messages Larysa Zaremba
2026-02-24 7:12 ` [Intel-wired-lan] " R, Bharath
2026-02-24 17:17 ` Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 07/15] idpf: remove 'vport_params_reqd' field Larysa Zaremba
2026-02-23 17:16 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 08/15] idpf: refactor idpf to use libie_pci APIs Larysa Zaremba
2026-02-23 17:16 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 09/15] idpf: refactor idpf to use libie control queues Larysa Zaremba
2025-12-11 3:42 ` Tantilov, Emil S
2025-12-15 16:10 ` Larysa Zaremba
2026-02-23 17:18 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 10/15] idpf: make mbx_task queueing and cancelling more consistent Larysa Zaremba
2026-02-23 17:16 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 11/15] idpf: print a debug message and bail in case of non-event ctlq message Larysa Zaremba
2026-02-23 17:16 ` [Intel-wired-lan] " Salin, Samuel
2025-11-17 13:48 ` [PATCH iwl-next v5 12/15] ixd: add basic driver framework for Intel(R) Control Plane Function Larysa Zaremba
2025-11-17 14:18 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-17 14:40 ` Larysa Zaremba
2026-02-24 7:02 ` R, Bharath
2025-11-17 13:48 ` [PATCH iwl-next v5 13/15] ixd: add reset checks and initialize the mailbox Larysa Zaremba
2025-11-17 14:21 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-17 14:42 ` Larysa Zaremba
2025-11-17 14:47 ` Loktionov, Aleksandr
2026-02-24 7:00 ` R, Bharath
2025-11-17 13:48 ` [PATCH iwl-next v5 14/15] ixd: add the core initialization Larysa Zaremba
2026-02-24 6:57 ` [Intel-wired-lan] " R, Bharath
2025-11-17 13:48 ` [PATCH iwl-next v5 15/15] ixd: add devlink support Larysa Zaremba
2025-11-17 14:28 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-11-18 6:58 ` Jacob Keller
2026-02-24 5:36 ` R, Bharath
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=20251117134912.18566-3-larysa.zaremba@intel.com \
--to=larysa.zaremba@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jayaprakash.shanmugam@intel.com \
--cc=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=madhu.chittim@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=natalia.wochtman@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=sridhar.samudrala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®