From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "sakoman@gmail.com" <sakoman@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>
Subject: Re: [PATCH 1/1] ASoC: TWL4030: Fix Analog capture path for AUXR
Date: Tue, 19 May 2009 10:57:22 +0100 [thread overview]
Message-ID: <20090519095722.GA26649@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03056A1739@dbde02.ent.ti.com>
On Tue, May 19, 2009 at 03:18:09PM +0530, Aggarwal, Anuj wrote:
> What should be the quickest way to merge all the ASoC patches which have come after my 2.6.29-rc3 release? I have a found a solution for my tuck noise problem now but cannot apply the patch as it is, because the tip has moved ahead from my baseline by several commits. I cannot move my baseline so have to pull only sound/soc related patches.
> Is there any repository where I will find only asoc related patches? Or what should be the ideal way to handle this?
You want the topic/asoc branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
That'll have some additional stuff from mainline due to some merge ups
of ALSA-wide stuff but it should all be safe given that it's targetting
2.6.30.
prev parent reply other threads:[~2009-05-19 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 7:51 [PATCH 0/1] ASoC: TWL4030: fix analog right microphone path Peter Ujfalusi
2009-05-19 7:51 ` [PATCH 1/1] ASoC: TWL4030: Fix Analog capture path for AUXR Peter Ujfalusi
2009-05-19 8:50 ` Mark Brown
2009-05-19 9:48 ` Aggarwal, Anuj
2009-05-19 9:57 ` 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=20090519095722.GA26649@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=peter.ujfalusi@nokia.com \
--cc=sakoman@gmail.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.