| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 30 Apr 2008 18:32:52 -0400 From: mkrufky@...uxtv.org To: bunk@...nel.org Cc: mchehab@...radead.org, mingo@...e.hu, linux-kernel@...r.kernel.org Subject: Re: [patch] dvb: build failure fix Adrian Bunk wrote: > On Wed, Apr 30, 2008 at 04:52:14PM -0300, Mauro Carvalho Chehab wrote: > >> On Wed, 30 Apr 2008 15:31:42 -0400 >> mkrufky@...uxtv.org wrote: >> >> >>>> Are there actually reports from users running into this problem? >>>> >> No. >> >> Yet, the configuration may be valid. If you have a board with tda8290, it >> _will_ need another chip, like tda827x. >> >> In the past, both tda8290 and tda827x were handled by the same driver, and >> worked for analog only. >> >> So, IMO, this is a regression. >> ... >> > > drivers/media/ is the part of the kernel with the most fragile kconfig > constructs. > > And we are talking about bringing a solution into -stable that has never > and will never be in mainline. > > A compile error in a configuration without practical relevance isn't a > huge problem, and I'd vote for leaving -stable unchanged. I agree wholeheartedly -- we should not change the build procedure for the -stable series. I hope nobody was seriously considering throwing in this sort of monkey wrench to a stable kernel. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists