From: Paul Mackerras <paulus@samba.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] keywest: Convert to new-style i2c driver
Date: Wed, 22 Apr 2009 19:34:40 +1000 [thread overview]
Message-ID: <18926.58544.374626.696097@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20090421114853.7a9d82c1@hyperion.delvare>
Jean Delvare writes:
> Not removing it now has a high risk of developers continuing to ignore
> the deprecation warnings and adding new legacy drivers, which I then
> must convert to the new model. This never ends.
>
> I know my behavior may seem a bit rude, but apparently this is the only
> way to get things to actually happen. I've been waiting for over a year
> already!
I sympathize, but throwing disruptive changes into Linus' tree when
we're past -rc3 is not the way to solve the problem.
The way to solve the problem is to (a) publish a branch where you put
the stuff you're going to ask Linus to pull in the next merge window,
(b) push a commit there that removes the legacy interfaces, (c) ask
Stephen Rothwell to include that branch in linux-next.
The linux-next tree gets built for a wide range of architectures and
configs, and any breakages get noticed and fixed pretty quickly.
Getting the removal of the legacy interfaces into linux-next will do
more in a week than a year's worth of deprecation warnings. :)
> I don't think the risk is that high, at least not for sound drivers.
> The conversions are fairly easy and if something really went wrong,
> fixing it is a matter of minutes.
We're past -rc3 now. This is not the time for pushing this sort of
change into Linus' tree. Ask Linus if you don't believe me.
> I have converted all remaining drivers by now:
> http://i2c.wiki.kernel.org/index.php/Legacy_drivers_to_be_converted
> It's really only a matter of getting them tested in time now. Given
> that most drivers are powermac ones, what I really need here is
> powermac users/maintainers to test my patches and report success or
> failure.
OK, but please work in your next branch and linux-next, not Linus'
tree.
Paul.
next prev parent reply other threads:[~2009-04-22 9:34 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 [this message]
2009-04-22 12:04 ` Jean Delvare
2009-04-22 12:56 ` Paul Mackerras
2009-04-22 14:24 ` Takashi Iwai
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=18926.58544.374626.696097@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=alsa-devel@alsa-project.org \
--cc=khali@linux-fr.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tiwai@suse.de \
/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