-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/21/14, 9:50 AM, Jean Delvare wrote:
Hi Alex,
Le Tuesday 20 May 2014 à 22:37 +0200, Alexander Graf a écrit :
On 20.05.14 22:21, Jean Delvare wrote:
So may I disable CONFIG_RTC_DRV_MOXART from all out kernels?
Yes, please.
Done.
I usually go through things that can be set as =m and just activate them to have as much hardware support available as possible :).
Well, please stop doing that ;-) Upstream is notoriously bad at limiting drivers to the systems on which they are actually useful (or maybe they are not that bad but still not good enough to my taste.) So in many cases new drivers are only needed in a subset of our kernels, or even none of them.
It's on purpose and it's infuriating. I've tried to submit patches to narrow hardware support to platforms which can actually use it and have been refused due to "build coverage." What use build coverage is when the hardware will never run on it is beyond my comprehension, but I just let it drop.
I know it takes some time to decide for each new driver whether it should be enabled or not. But it pays quickly by reducing the risk of build failure (which in fact are sometimes a hint that you enabled the driver on an architecture it wasn't meant for, so it was never tested) and speeding up the future builds and updates.
Thanks again for all your work here. Seeing how much effort you've needed to put into it has pushed me to start more aggressively documenting config changes in the commit messages. The config-options.txt attempt was a nice idea, but it fell apart pretty quickly. Hopefully this won't. If something was enabled because it's a new driver and looked sane, I'll document it as such. I've started doing a bit of research on whether hardware is supported on a particular arch, but sometimes it can be a dead end: How does one know if a PCI device will only ever be found on e.g. ppc64? Even if it's only initially shipped there, it can be recycled into other hardware later. I'd like to get other folks on board with this. Hopefully with a standard format moving forward (it doesn't need to be what I'm doing now, but it seemed sane.) - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQIcBAEBAgAGBQJThJQDAAoJEB57S2MheeWy3cgQALHHrRXFmpsFSqCredRb3l9E 2iOwFlwaE9bYNvKTHSPygH1kOvLWwAEAL9dYzYAGqpQE6NcAG2i0BJsLGIeezzGV 0OEl5YQf1LvGifrSpgl/EkfImuXZhO4aRzbuifJ4ZRb4fIV6Z+xiDSgXzjALpWQB mDp9ZG6X6SIJ4O6WnwLkAcvwIlmJ+4Wb2rok5V1hYwpRXSJvSdJHLLXHk2ZnGawN vPimodYSoMXxnxDsn1U8UJXf/mrnYBWc9QhKXcsNA+0rymlKKpc3CNPHJ+GIas6y U/U1Vj04IncFfN3CxCWmoCRH5KkWrIrfMEQyOMP4tEG9y5aysCB6ZvZAS3+GFdTo 7qH46GJ10HBngWf+V8XRQX6Hk/VBsPHfPtP03jjrwM+SWzgdAfh0QJh7pV25QB+h T2Vyw2W55Zf8zV+8j00PaKggkcmjPMzlB8e+xvxctplHb2zXb5M9js1EcRFcKGMe n1HcJk1tQ2pFTZwPiMY9UYN4iCvbhvCTqUrHnQr5dF4NLQdcHjFM4MeF0EaRNezf 4vbrVbB0+bfAPbQCKHakCWY6PiDcfwvROFZAXV/QWwUcQjkO2FbvcahPl3VbBgYY A5xfBjYl6GO/t+4PgtLMANm+FuwRXjEGywKzMyPpI4FjgMI6A5FjxtgRhw/2F95r gadFq6c22rwjwSVwdLDO =FPjv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org