| 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
| ||
|
Message-ID: <20070514202419.33a90f57@hyperion.delvare> Date: Mon, 14 May 2007 20:24:19 +0200 From: Jean Delvare <khali@...ux-fr.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Antonino Ingargiola <tritemio@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.22-rc1 Hello Linus, On Mon, 14 May 2007 09:30:19 -0700 (PDT), Linus Torvalds wrote: > On Mon, 14 May 2007, Jean Delvare wrote: > > > > This is a side effect of an i2c-core cleanup. This is already fixed in > > lm_sensors 2.10.3 (libsensors.so.3.1.3). > > So apparently that fixed it, but in general we do not allow these kinds of > "need to have new xyz with new kernel". Sure, we don't allow that. Except for xfsprogs in 2.6.1, procps in 2.6.4, oprofile in 2.6.13 and udev in 2.6.19, of course. > Kernels are supposed to be backwards compatible. Jean, what was it that > changed, and why can't we just make them appear the same? > > It may be that something like a sensors package isn't important enough to > worry about (the machine still *works*, and everything else won't notice), > but if it's a simple matter of adding some random file to /sysfs, we > should just do it. We already have CONFIG_SYSFS_DEPRECATED for that. -- 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