[Bug 858067] Socketcan removed as colateral damage with patch 33d736f0040a00b756454f084b199f87cf960b2c(config: disabled CONFIG_SPI and CONFIG_IIO on non-ARM architectures)

https://bugzilla.novell.com/show_bug.cgi?id=858067 https://bugzilla.novell.com/show_bug.cgi?id=858067#c17 Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |jdelvare@suse.com Resolution|FIXED | AssignedTo|kernel-maintainers@forge.pr |jdelvare@suse.com |ovo.novell.com | --- Comment #17 from Jean Delvare 2014-04-29 09:35:19 UTC --- (In reply to comment #1)

While we can't change configs of already released products, (...)

This is not quite true. Nothing prevents us from changing the kernel configuration as part of a maintenance update. This is no different from adding or removing patches as needed. As long as we have a good reason for the change, and there is no risk of introducing a regression for other users, this is something we can do. In this specific case, CAN support has been enabled in openSUSE kernels since version 11.0. Suddenly removing support in openSUSE 13.1 while some users were relying on it is a regression. As such, I believe it deserves to be fixed in released products, in this case openSUSE 13.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.