linux-kernel - Re: [PATCH] OMAP: I2C driver for TI OMAP boards #2

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>] [day] [month] [year] [list]

Message-Id: <20060802092759.66aa23c4.khali@linux-fr.org>
Date:	Wed, 2 Aug 2006 09:27:59 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	David Brownell <david-b@...bell.net>
Cc:	Komal Shah <komal_shah802003@...oo.com>, akpm@...l.org,
	gregkh@...e.de, i2c@...sensors.org, imre.deak@...ia.com,
	juha.yrjola@...idboot.com, linux-kernel@...r.kernel.org,
	r-woodruff2@...com, tony@...mide.com
Subject: Re: [PATCH] OMAP: I2C driver for TI OMAP boards #2

Hi David,

> > The "and could be patched later" way has been tried before, and I'm not
> > going there again. Later happened to be "never" or at least "too late"
> > more often than not.
> 
> Well, you've seen my basic review.  As for "later", it's quite routine;
> that's what "submit early and often" means.  That whole ext4 devel
> cycle depends on using "later" intelligently.

Releasing "early and often" was never an excuse to release buggy code.
It is (to me, at least) about adding functionalities one at a time,
rather than waiting to be full-featured before releasing first.

As for the "later", there are areas where it is known not to work, e.g.
documentation - or more generally, everything which is optional from a
functional point of view. I do expect functional bugs to be fixed
later when they bite the users, but I am more skeptical about cleanups
and documentation.

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