From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mmp: support ssp in pxa168
Date: Thu, 11 Mar 2010 10:58:05 +0000 [thread overview]
Message-ID: <20100311105804.GD2585@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <f17812d71003110020g67bb7fd6tfe1381294b6cfe8f@mail.gmail.com>
On Thu, Mar 11, 2010 at 04:20:35PM +0800, Eric Miao wrote:
> On Wed, Mar 10, 2010 at 10:28 PM, Mark Brown
> > cycle? ?I can apply the patches on a branch by themselves which can also
> > be pulled into the PXA tree if needed.
> I'd expect there to be some merge conflicts I need to solve along with
> my cleaning up of the SSP code. That said, it's better to go via -pxa
> tree and get the multi-codec work solved in linux-next?
That's not going to be possible with at least the machine driver - if
it's only present in one tree we can't do fixups in the other. This is
why I'm saying put it on a branch and merge it into both trees, that way
both trees have the code in them as though things had been merged into
mainline already so problems are much less likely.
> Mark, could you please point me the reference to the multi-codec work
> so I can have a rough feeling of the possible merge issues?
There's a branch in Liam's git tree (still sketching out the goal rather
than the finished product):
git://git.kernel.org/pub/scm/linux/kernel/git/lrg/asoc-2.6.git
Big thing is that there's most likely going to be at least cosmetic
changes to how cards are registered.
next prev parent reply other threads:[~2010-03-11 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 13:14 [PATCH 2/4] mmp: support ssp in pxa168 Haojian Zhuang
2010-03-10 14:28 ` Mark Brown
2010-03-11 8:20 ` Eric Miao
2010-03-11 10:58 ` Mark Brown [this message]
2010-03-11 11:11 ` [alsa-devel] " Liam Girdwood
2010-03-16 11:49 ` Eric Miao
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=20100311105804.GD2585@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).