From: Mark Brown <broonie@sirena.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Peter Ujfalusi <peter.ujfalusi@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/1] ASoC patch on top of linux-omap 2.6.29-rc1 (TWL4030 related)
Date: Fri, 16 Jan 2009 13:12:14 +0000 [thread overview]
Message-ID: <20090116131213.GF7554@sirena.org.uk> (raw)
In-Reply-To: <20090116072712.GL4128@atomide.com>
On Fri, Jan 16, 2009 at 09:27:12AM +0200, Tony Lindgren wrote:
> In general that would be best, as then I know it's been acked and on
> it's way to the mainline kernel via alsa already. Meaning it's safe
> for me to apply to linux-omap without increasing the diff to mainline
> kernel.
Linus has already merged it, FWIW.
prev parent reply other threads:[~2009-01-16 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 6:14 [PATCH 0/1] ASoC patch on top of linux-omap 2.6.29-rc1 (TWL4030 related) Peter Ujfalusi
2009-01-16 6:14 ` [PATCH 1/1] ASoC: Fix the power update function for snd_soc_dapm_value_mux Peter Ujfalusi
2009-01-16 6:21 ` [PATCH 0/1] ASoC patch on top of linux-omap 2.6.29-rc1 (TWL4030 related) Peter Ujfalusi
2009-01-16 7:27 ` Tony Lindgren
2009-01-16 13:12 ` 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=20090116131213.GF7554@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox