LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Linux I2C" <i2c@lm-sensors.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] i2c updates for 2.6.25
Date: Sun, 3 Feb 2008 16:09:48 +0100	[thread overview]
Message-ID: <20080203160948.4182200c@hyperion.delvare> (raw)
In-Reply-To: <9e4733910801280620t16ceb391vcc8e10ba6bbea183@mail.gmail.com>

On Mon, 28 Jan 2008 09:20:13 -0500, Jon Smirl wrote:
> On 1/28/08, Jean Delvare <khali@linux-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

      reply	other threads:[~2008-02-03 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 17:27 Jean Delvare
2008-01-27 17:36 ` Jon Smirl
2008-01-28  9:43   ` Jean Delvare
2008-01-28 14:20     ` Jon Smirl
2008-02-03 15:09       ` Jean Delvare [this message]

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=20080203160948.4182200c@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=i2c@lm-sensors.org \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] i2c updates for 2.6.25' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).