IB/ipath: Change use of constants for TID type to defined values
Define pkt rcvd 'type' in a way consistent with HW spec and chips. The hardware considers received packets of type 0 to be expected, and type 1 to be eager. The driver was calling the ipath_f_put_tid functions using a variable called 'type' set to 0 for eager and to 1 for expected packets. Worse, the iba6110 and iba6120 drivers used those values inconsistently. This was quite confusing. Now everything is consistent with the hardware. Signed-off-by:Dave Olson <dave.olson@qlogic.com> Signed-off-by:
Roland Dreier <rolandd@cisco.com>
Showing
- drivers/infiniband/hw/ipath/ipath_file_ops.c 8 additions, 4 deletionsdrivers/infiniband/hw/ipath/ipath_file_ops.c
- drivers/infiniband/hw/ipath/ipath_iba6110.c 6 additions, 4 deletionsdrivers/infiniband/hw/ipath/ipath_iba6110.c
- drivers/infiniband/hw/ipath/ipath_iba6120.c 8 additions, 6 deletionsdrivers/infiniband/hw/ipath/ipath_iba6120.c
- drivers/infiniband/hw/ipath/ipath_init_chip.c 2 additions, 1 deletiondrivers/infiniband/hw/ipath/ipath_init_chip.c
Loading
Please register or sign in to comment