From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: ASoC V2: disable automatic volume control in the CS4270 sound driver
Date: Sat, 23 Aug 2008 14:39:06 +0100 [thread overview]
Message-ID: <20080823133906.GA19258@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <48AF2D39.6000701@freescale.com>
On Fri, Aug 22, 2008 at 04:18:49PM -0500, Timur Tabi wrote:
> Did you guys forget about this patch? I don't see it in asoc-v2-dev.
Just lost in the shuffle. I've managed to locate a copy in my archives
and applied it now. When sending reminders like this the more normal
approach is to resubmit the entire patch - apart from anything else,
there's a reasonable chance that if the patch was lost the original mail
has been lost as well so it'll need to be resent anyway.
It really would be better if changes like this could also be made to
mainline as well - it is much easier to review the differences between
the two branches if there aren't changes like this one that are
unrelated to the API changes mixed in as well.
prev parent reply other threads:[~2008-08-23 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 16:22 [PATCH] ALSA: ASoC V2: report error if DMA doesn't start in FSL MPC8610 sound drivers Timur Tabi
2008-08-07 16:22 ` [PATCH] ALSA: ASoC V2: disable automatic volume control in the CS4270 sound driver Timur Tabi
2008-08-07 16:22 ` [PATCH] ALSA: ASoC V2: trim SSI sysfs statistics in Freescale MPC8610 sound drivers Timur Tabi
2008-08-08 10:54 ` [PATCH] ALSA: ASoC V2: disable automatic volume control in the CS4270 sound driver Mark Brown
2008-08-08 15:03 ` Timur Tabi
2008-08-22 21:18 ` Timur Tabi
2008-08-23 13:39 ` Mark Brown [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=20080823133906.GA19258@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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 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.