Okay, this information is good to know.
So I imagine we need
29cb3b8d95c7 ixgbe: add E610 implementation of FW recovery mode
85308d999c4b ixgbe: fix memory leak and use-after-free in
ixgbe_recovery_probe() (fixes 29cb3b8d95c7)
because of
b85936e ixgbe: initialize aci.lock before it's used
316ba68 ixgbe: destroy aci.lock later within ixgbe_remove path
right?
Both b85936e and 316ba68 are only really needed after 337369f8ce9e
("locking/mutex: Add MUTEX_WARN_ON() into fast path") right? So maybe we
can get away with not having them, as noble does not carry this patch.
Saying that, if you build a test kernel with just the first two fixups:
b1e44b4 ixgbe: fix media cage present detection for E610 device
4020659 ixgbe: fix media type detection for E610 device
does this build and test correctly? You could just use those two and
drop the other two before it all snowballs and increases the risk of
regression any further.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131265
Title:
[SRU] ixgbe: Add support for E610 in Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131265/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
