Fix GRO_DROP deprecation in Linux v5.12. #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The check on the return value of rtw_napi_gro_receive() is not necessary any more for kernels > v5.12.
There is another pull request #64 that checks whether return value is GRO_MERGED_FREE and treats that as an error condition. But I don't think that is the correct behavior, since the underlying kernel API dev_gro_receive(), defined in net/core/dev.c also returns that status in previous Linux versions (e.g., v5.11.21), and yet the driver did not treat it as an error conditions previously. This pull request should preserve the original semantics of the driver code.