linux-kernel - Re: [GIT PULL] i2c updates for 2.6.25

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080203160948.4182200c@hyperion.delvare>
Date:	Sun, 3 Feb 2008 16:09:48 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	"Jon Smirl" <jonsmirl@...il.com>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Linux I2C" <i2c@...sensors.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] i2c updates for 2.6.25

On Mon, 28 Jan 2008 09:20:13 -0500, Jon Smirl wrote:
> On 1/28/08, Jean Delvare <khali@...ux-fr.org> wrote:
> > The status is that I want to give people some time to comment on my
> > modalias patches before I merge them. I also didn't have the time to
> > look into the latest patches you sent yet, and I'd rather merge
> > everything at once. So the merge window for this is rather 2.6.26.
> 
> Delaying these until 2.6.26 which won't be final until 2009 forces us
> to ship boxes using a private kernel. These patches have been around
> since November. Does it really take over a year to get these changes
> in?

It can even take forever when people piss me off.

This patch set affects 5 different subsystems and several
dozen drivers. All these drivers have been (ab)using the previous
and current I2C device naming and device/driver matching logic in
different ways, and have different expectations and needs. I'm not
changing this now to break it again next month when other kernel
developers will complain that the new model doesn't work for them.

-- 
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/