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: Mon, 31 Jul 2006 21:25:32 +0200	[thread overview]
Message-ID: <20060731212532.810a39f8.khali@linux-fr.org> (raw)
In-Reply-To: <200607310941.01340.david-b@pacbell.net>

> > It doesn't work like this, sorry. The merge window for 2.6.18 is
> > closed. The driver needs to be reviewed before it is merged. So the
> > best you can hope for is -mm soon, and 2.6.19.
> 
> So there's been a change from the "new drivers can be merged late"
> policy?  News to me if so.  Not that this is a particularly new
> driver of course, or at all unstable.

This is my own policy for i2c drivers as the maintainer of the i2c
subsystem. I simply observed that new drivers cause much more late-rc
trouble than all other changes. So in order to let things stabilize
quickly, I don't take new drivers after -rc1. I see no reason why new
drivers would be allowed to bypass the -mm staging anyway.

If people want their drivers merged, they have to send them early. And
if they think I don't review them quickly enough (which is true) they
have to find other reviewers. There is no reason why I would have to
review every new i2c driver. As a matter of fact, I just don't have the
time to do so.

> > Indeed, this is no good. If you want things to improve, please help by
> > reviewing Komal's driver. I think I understand you already commented on
> > it, but I'd like you to really review it, and add a formal approval to
> > it (e.g. Signed-off-by or Acked-by). Then I'll review it for merge.
> 
> Review it again?  I'll try to make some time to help there, but
> it's unlikely I'll notice significant issues that seem to me
> worth holding up the upstream merge.  Certainly none that make
> up for the problems caused by having the kernel.org tree be all
> but unusable for OMAP work, and couldn't be patched later.

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.

And again maybe other subsystem maintainers have other policies, I
don't really care. I do the things the way I think works better. Anyone
not happy with that will have to help me a lot with the i2c patches
before I listen to him/her.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2006-07-31 19:25 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 [this message]
     [not found]         ` <200607311713.09820.david-b@pacbell.net>
2006-08-02  7:27           ` Jean Delvare
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=20060731212532.810a39f8.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