public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: David Brownell <david-b@pacbell.net>
Cc: Komal Shah <komal_shah802003@yahoo.com>,
	akpm@osdl.org, gregkh@suse.de, i2c@lm-sensors.org,
	imre.deak@nokia.com, juha.yrjola@solidboot.com,
	linux-kernel@vger.kernel.org, r-woodruff2@ti.com,
	tony@atomide.com
Subject: Re: [PATCH] OMAP: I2C driver for TI OMAP boards #2
Date: Wed, 2 Aug 2006 09:27:59 +0200	[thread overview]
Message-ID: <20060802092759.66aa23c4.khali@linux-fr.org> (raw)
In-Reply-To: <200607311713.09820.david-b@pacbell.net>

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

  parent reply	other threads:[~2006-08-02  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1154066134.13520.267064606@webmail.messagingengine.com>
2006-07-31 14:33 ` [PATCH] OMAP: I2C driver for TI OMAP boards #2 David Brownell
2006-07-31 16:13   ` Jean Delvare
2006-07-31 16:41     ` David Brownell
2006-07-31 19:10       ` Russell King
2006-07-31 23:55         ` David Brownell
2006-08-01 14:33           ` Tony Lindgren
2006-07-31 19:25       ` Jean Delvare
     [not found]         ` <200607311713.09820.david-b@pacbell.net>
2006-08-02  7:27           ` Jean Delvare [this message]
2006-07-31 23:53     ` David Brownell
2006-08-02 15:50       ` Jean Delvare
2006-08-02 19:18         ` David Brownell
2006-08-03  9:19           ` Jean Delvare
2006-08-03 14:30             ` David Brownell
2006-08-04  8:31               ` Jean Delvare
     [not found] <1153980844.20163.266978546@webmail.messagingengine.com>
2006-08-02 15:34 ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060802092759.66aa23c4.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=akpm@osdl.org \
    --cc=david-b@pacbell.net \
    --cc=gregkh@suse.de \
    --cc=i2c@lm-sensors.org \
    --cc=imre.deak@nokia.com \
    --cc=juha.yrjola@solidboot.com \
    --cc=komal_shah802003@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r-woodruff2@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox