Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Jean Delvare <khali@linux-fr.org>,
	linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] keywest: Convert to new-style i2c driver
Date: Wed, 22 Apr 2009 16:24:56 +0200	[thread overview]
Message-ID: <s5hbpqoahqf.wl%tiwai@suse.de> (raw)
In-Reply-To: <18927.5140.888171.141615@cargo.ozlabs.ibm.com>

At Wed, 22 Apr 2009 22:56:52 +1000,
Paul Mackerras wrote:
> 
> Jean Delvare writes:
> 
> > > I sympathize, but throwing disruptive changes into Linus' tree when
> > > we're past -rc3 is not the way to solve the problem.
> > 
> > We're past -rc3 because people discuss instead of testing my patches.
> > Otherwise everything would be merged already.
> 
> Well, no.  The first conversion patch that I saw was posted after the
> merge window had already closed, on 8 April.
> 
> > And really, these changes (sound drivers) don't qualify as disruptive.
> > You might argue about the thermal management driver changes if you
> > want. But sound drivers, nothing bad will happen if they accidentally
> > break.
> 
> That's what we call a "regression". :)

Well, I believe it's even better to merge this conversion patch now,
from practical viewpoint.

If we get a regression for this particular device, the patch can be
simply reverted as long as the legacy i2c framework exists.  If we
merge everything, i.e. the conversion and the removal of old i2c
binding, at the same time in 2.6.31 merge window, reverting is much
harder.

So, I agree with that the removal of old i2c binding can be postponed
to 2.6.31.  It can be done on linux-next from now on, and we can keep
watching.  But, this small conversion patch can be more easily managed
in 2.6.30.


thanks,

Takashi

  reply	other threads:[~2009-04-22 14:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 20:56 [PATCH] keywest: Convert to new-style i2c driver Jean Delvare
2009-04-20 22:34 ` Paul Mackerras
2009-04-21  6:33   ` Takashi Iwai
2009-04-21  9:33     ` Paul Mackerras
2009-04-21  9:36       ` Takashi Iwai
2009-04-21  9:48     ` Jean Delvare
2009-04-21  9:56       ` Wolfram Sang
2009-04-22  9:34       ` Paul Mackerras
2009-04-22 12:04         ` Jean Delvare
2009-04-22 12:56           ` Paul Mackerras
2009-04-22 14:24             ` Takashi Iwai [this message]
2009-04-23  9:54             ` Jean Delvare
2009-04-21  6:31 ` Takashi Iwai
2009-04-21  9:23   ` Jean Delvare
2009-04-21  9:30     ` Takashi Iwai
2009-04-21  9:44     ` 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=s5hbpqoahqf.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=khali@linux-fr.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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