The included patch fixes a possible failure to detect the CAN-USB/* device after a reboot. Being a fix for a complete device failure I believe it qualifies for the -stable kernel series. I'm sending this patch as a RFC only with "Cc: stable@xxxxxxxxxxxxxxx" for the following reasons: - The patch size exceeds the maximum size of 100 lines for a stable patch mentioned here: https://www.kernel.org/doc/html/v6.12/process/stable-kernel-rules.html - The patch carries a Fixes: tag for the commit where the support for the CAN-USB/3-FD hit the 6.6 mainline kernel even if the erroneous code was present in previous releases. I have done this because the internal structure of the driver changed with this commit. Backporting to earlier kernels would need some adjustment of the patch. For the moment it would be fine for me to get the patch in the mainline kernel and the -stable kernels down to 6.6. Earlier kernels need to be addressed with adjusted patches if this is feasible. Any comments on how to proceed further? Will the patch size disqualify the patch for inclusion in the -stable kernels? Stefan Mätje (1): can: esd_usb: Fix not detecting version reply in probe routine drivers/net/can/usb/esd_usb.c | 122 +++++++++++++++++++++++++--------- 1 file changed, 92 insertions(+), 30 deletions(-) base-commit: 38f83a57aa8e644f37a88d4771d756303cfa7365 -- 2.34.1
