| 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: Thu, 7 Aug 2008 23:06:52 +0200 From: Jean Delvare <khali@...ux-fr.org> To: "Michael Krufky" <mkrufky@...uxtv.org> Cc: "Sam Ravnborg" <sam@...nborg.org>, "D. Kelly" <user.kernel@...il.com>, "mailing list: linux-kernel" <linux-kernel@...r.kernel.org>, "Linux I2C" <i2c@...sensors.org> Subject: Re: Problem with restricted I2C algorithms in kernel 2.6.26! Hi Michael, On Thu, 7 Aug 2008 15:03:36 -0400, Michael Krufky wrote: > I agree with Trent and D.Kelly > > These options should be made available to the user -- We should go > with the patch that Jean posted, "Subject: i2c: Let users select > algorithm drivers manually again" -- this is a fair compromise for > both sides -- users that dont know should leave the automatic > selection enabled. Users that know better can disable the automatic > selection and enable what they need. > > The statement, "just have the external driver merged into the kernel" > is not a solution. Why not, please? A vast majority of drivers work fine that way today. I am still waiting for someone to give me a good reason why some other drivers supposedly can't be merged upstream (something better than "believe me, it's impossible".) > Removing the option to build those additional algos is a regression, IMHO Will be addressed soon, do not worry. -- Jean Delvare -- 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