| commit | 74608fc98d2856fa7201a498b61c9dd9455b504a | |
| author | Prashant Sreedharan <prashant@broadcom.com> | |
| Thu, 28 Jan 2016 08:11:20 +0000 (28 03:11 -0500) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Sat, 30 Jan 2016 01:28:39 +0000 (29 17:28 -0800) | ||
| tree | 5be7383376927f7afa073d57bf7bd5bd5883ebd0 | treesnapshot (tar.gz zip) |
| parent | df3eb6cd68924d5ea16032faecae7fb775f67883 | commitdiff |
bnxt_en: Ring free response from close path should use completion ring
Use completion ring for ring free response from firmware. The response
will be the last entry in the ring and we can free the ring after getting
the response. This will guarantee no spurious DMA to freed memory.
Signed-off-by: Prashant Sreedharan <prashant@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Use completion ring for ring free response from firmware. The response
will be the last entry in the ring and we can free the ring after getting
the response. This will guarantee no spurious DMA to freed memory.
Signed-off-by: Prashant Sreedharan <prashant@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| drivers/net/ethernet/broadcom/bnxt/bnxt.c | diffblobblamehistory |