1. 29 8月, 2017 1 次提交
  2. 26 7月, 2017 1 次提交
    • J
      ftgmac100: return error in ftgmac100_alloc_rx_buf · 6cee9d64
      Joel Stanley 提交于
      The error paths set err, but it's not returned.
      
      I wondered if we should fix all of the callers to check the returned
      value, but Ben explains why the code is this way:
      
      > Most call sites ignore it on purpose. There's nothing we can do if
      > we fail to get a buffer at interrupt time, so we point the buffer to
      > the scratch page so the HW doesn't DMA into lalaland and lose the
      > packet.
      >
      > The one call site that tests and can fail is the one used when brining
      > the interface up. If we fail to allocate at that point, we fail the
      > ifup. But as you noticed, I do have a bug not returning the error.
      Acked-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NJoel Stanley <joel@jms.id.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6cee9d64
  3. 25 7月, 2017 2 次提交
  4. 19 4月, 2017 8 次提交
  5. 12 4月, 2017 10 次提交
  6. 11 4月, 2017 12 次提交
  7. 07 4月, 2017 6 次提交