From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: linux-next: manual merge of the sound-asoc tree with the s5p tree
Date: Mon, 5 Dec 2011 10:28:08 +0000 [thread overview]
Message-ID: <20111205102807.GA11150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111205130102.aec262d85aa6b47b0aec7011@canb.auug.org.au>
On Mon, Dec 05, 2011 at 01:01:02PM +1100, Stephen Rothwell wrote:
> Just context changes. I fixed it up (see below) and can carry the fix as
> necessary.
Thanks!
next prev parent reply other threads:[~2011-12-05 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 2:01 linux-next: manual merge of the sound-asoc tree with the s5p tree Stephen Rothwell
2011-12-05 10:28 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-31 0:56 Stephen Rothwell
2010-12-31 1:59 ` Kukjin Kim
2010-10-11 2:35 Stephen Rothwell
2010-10-11 7:33 ` Kukjin Kim
2010-10-11 8:33 ` Stephen Rothwell
2010-10-11 22:26 ` Kukjin Kim
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=20111205102807.GA11150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
/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.