osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

No reason not to use etype_vals for an Ethertype field. 

Maybe there was an issue on Windows back in the old days, when 1) we
didn't have a shared libwireshark library from which to import functions
and data variables and thus you couldn't get variables such as
etype_vals in a plugin and 2) the Infiniband dissector was a plugin, but
neither of those are the case any more.

Change-Id: Id8b82886317bd36a32ad1e1591673623696d4808
Reviewed-on: https://code.wireshark.org/review/19530
Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
Guy Harris 2017-01-03 18:09:49 -08:00
parent ab286246dc
commit a2d6fb94fc
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
epan/dissectors/packet-infiniband.c
View File

@ -5710,7 +5710,7 @@ void proto_register_infiniband(void)
},
{ &hf_infiniband_etype, {
"Ethertype", "infiniband.rwh.etype",
FT_UINT16, BASE_HEX, NULL /*VALS(etype_vals)*/, 0x0, "Type", HFILL }
FT_UINT16, BASE_HEX, VALS(etype_vals), 0x0, "Type", HFILL }
},
/* Reliable Datagram Extended Transport Header (RDETH) */