From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rongrong Cao <rrcao@ambarella.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
trivial@kernel.org
Subject: Re: [PATCH for-2.6.32] sound dapm: fix checking for external widgets bug
Date: Fri, 10 Jul 2009 20:19:26 +0100 [thread overview]
Message-ID: <20090710191925.GA5916@sirena.org.uk> (raw)
In-Reply-To: <90B0CE4312136749B97EBEAF5764F87403C8F77A@ambarella-ex.ambarella.net>
On Tue, Jul 07, 2009 at 11:11:46PM -0700, Rongrong Cao wrote:
> From: Rongrong Cao rrcao@ambarella.com
> This patch is based on for-2.6.32
> In SOC DAPM layer of SOUND subsystem, when add signal route (in the function snd_soc_dapm_add_route() ),
> the original code has wrong logic when dapm layer check each widget whether an external one.
This still doesn't apply. It looks like your MUA is corrupting the
patch - it's MIME encoded everything and replaced all the tabs with
spaces which is causing all the patch application programs I have to get
confused. Documentation/email-clients.txt has some suggestions on how
to configure various MUAs to send patches cleanly. Personally I always
use git send-email. You probably also want to have a look at the
instructions in Documentation/SubmittingPatches with regard to the
formatting of your patch - the main thing being that the Signed-off-by
should go before the patch content.
In any case, I've manually applied the patch so no need to resubmit it.
I also notice that you've CCed trivial@kernel.org. Please don't do that
except for things that can't possibly cause bugs - a change like this
doesn't really qualify since while the code clearly looks buggy it's
always possible that the code is just obscure.
next prev parent reply other threads:[~2009-07-10 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 6:11 [PATCH for-2.6.32] sound dapm: fix checking for external widgets bug Rongrong Cao
2009-07-10 19:19 ` Mark Brown [this message]
2009-07-10 20:39 ` Jiri Kosina
2009-07-11 5:51 ` 答复: " Rongrong Cao
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=20090710191925.GA5916@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrcao@ambarella.com \
--cc=trivial@kernel.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