7:04 p.m.
On 15/07/2020 09:55, Geert Uytterhoeven wrote:
Indeed, it should be fixed at the core, not in an integration testing
tree.
BTW, did it show up in linux-next, too, or have I done a bad merge conflict
resolution?
Looking at linux-next, it appears tha|t efx_io_error_detected()||there
|| takes a pci_channel_state_t, so Bjorn's fix has already been applied
there, probably by way of merging pci/next (which applies a conjugate
fix to efx.c:||efx_io_error_detected()) and net-next (which moves the
function to efx_common.c).
For whatever reason renesas must've come up with a different merge
resolution, hence why they're seeing this.
-ed
|||||||||||||