On 11/17/2025 6:28 AM, Loktionov, Aleksandr wrote:
> 
> 
>> -----Original Message-----
>> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf
>> Of Larysa Zaremba
>> Sent: Monday, November 17, 2025 2:49 PM
>> To: intel-wired-lan@lists.osuosl.org; Nguyen, Anthony L
>> <anthony.l.nguyen@intel.com>
>> Cc: Lobakin, Aleksander <aleksander.lobakin@intel.com>; Samudrala,
>> Sridhar <sridhar.samudrala@intel.com>; Singhai, Anjali
>> <anjali.singhai@intel.com>; Michal Swiatkowski
>> <michal.swiatkowski@linux.intel.com>; Zaremba, Larysa
>> <larysa.zaremba@intel.com>; Fijalkowski, Maciej
>> <maciej.fijalkowski@intel.com>; Tantilov, Emil S
>> <emil.s.tantilov@intel.com>; Chittim, Madhu <madhu.chittim@intel.com>;
>> Hay, Joshua A <joshua.a.hay@intel.com>; Keller, Jacob E
>> <jacob.e.keller@intel.com>; Shanmugam, Jayaprakash
>> <jayaprakash.shanmugam@intel.com>; Wochtman, Natalia
>> <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>; Kitszel, Przemyslaw
>> <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: [Intel-wired-lan] [PATCH iwl-next v5 15/15] ixd: add devlink
>> support
>>
>> From: Amritha Nambiar <amritha.nambiar@intel.com>
>>
>> Enable initial support for the devlink interface with the ixd driver.
>> The ixd hardware is a single function PCIe device. So, the PCIe
>> adapter gets its own devlink instance to manage device-wide resources
>> or configuration.
>>
>> $ devlink dev show
>> pci/0000:83:00.6
>>
>> $ devlink dev info pci/0000:83:00.6
>> pci/0000:83:00.6:
>>   driver ixd
>>   serial_number 00-a0-c9-ff-ff-23-45-67
>>   versions:
>>       fixed:
>>         device.type MEV
>>       running:
>>         cp 0.0
>>         virtchnl 2.0
>>
> This commit mentions MEV without expansion.
> Kernel docs require expanding uncommon abbreviations.
> 

This is an example of the output of devlink, so if devlink literally
does print MEV, this should stay as-is. You could provide an area which
explains what each device type means and has the expanded definition.