From: Jean Delvare <khali@linux-fr.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] ASoC: Fix cs4270 error path
Date: Tue, 30 Sep 2008 11:38:55 +0200 [thread overview]
Message-ID: <20080930113855.10717f1d@hyperion.delvare> (raw)
In-Reply-To: <s5hfxniypz3.wl%tiwai@suse.de>
Hi Takashi,
On Tue, 30 Sep 2008 10:53:20 +0200, Takashi Iwai wrote:
> At Tue, 30 Sep 2008 10:31:37 +0200,
> Jean Delvare wrote:
> > I fear there's some confusion there. There are two different patches
> > fixing error paths in cs4270. One fixing a fallout from the new-style
> > i2c driver conversion (in cs4270_i2c_probe), under name "ASoC: Fix
> > another cs4270 error path". This one you pushed to Linus last night.
> >
> > But there's another one, named "ASoC: Fix cs4270 error path",
> > originally posted by myself on August 31st, fixing the error path of
> > cs4270_probe. This is the one Timur was just acking, but I do _not_ see
> > it in your queue, so I suspect you missed it. I can resend it if it
> > helps.
>
> Oh, OK, then I must have missed that. Could you repost?
Will do in a minute.
> And, this *must* go to 2.6.27, or not?
It could go in 2.6.27, certainly, but I wouldn't say it *must* go
there. The patch is "only" fixing an error path, which by definition
isn't supposed to be needed unless something unexpected happens, in
which case the driver probably won't work anyway. So it doesn't deserve
delaying 2.6.27, and sending a pull request to Linus for just that
patch would probably be overkill. But if you get the opportunity to
send such a pull request for another problem, then it makes sense to
include this cs4270 fix as well.
Anyway it's really up to you and Timur. I just happened to notice the
bug and posted a fix, but I'm not even using the driver myself.
> Frankly, this series of cs4270 patches have been hard to handle
> because it was always unclear what the patch is for.
> The description "It's for 2.6.x" is too ambiguous because it doesn't
> always mean the purpose but also can mean the based version of the
> patch. So, a more clear sign would be really helpful for me at the
> next time...
OK, sorry about that. I'll try to make things clearer next time.
--
Jean Delvare
next prev parent reply other threads:[~2008-09-30 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 12:42 [PATCH] ASoC: Fix cs4270 error path Jean Delvare
2008-09-22 12:29 ` Jean Delvare
2008-09-22 20:35 ` Timur Tabi
2008-09-27 16:09 ` Jean Delvare
2008-09-29 13:42 ` Timur Tabi
2008-09-29 13:48 ` Takashi Iwai
2008-09-30 8:31 ` Jean Delvare
2008-09-30 8:53 ` Takashi Iwai
2008-09-30 9:38 ` Jean Delvare [this message]
2008-09-30 11:08 ` Takashi Iwai
2008-09-30 14:25 ` Timur Tabi
2008-09-30 14:49 ` Takashi Iwai
2008-09-30 14:56 ` Timur Tabi
2008-09-30 15:03 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2008-09-30 9:40 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=20080930113855.10717f1d@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.