From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
linux-kernel@vger.kernel.org, ben-linux@fluff.org,
linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:26:37 +0000 [thread overview]
Message-ID: <20110311122637.GH1760@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTintYQ=qO3PALBL-bkiYKQFw0+JiW3=-oZmkRhZ1@mail.gmail.com>
On Fri, Mar 11, 2011 at 01:23:37PM +0100, Belisko Marek wrote:
> You're right. I think sending whole patch to help understand what
> I'm trying to do (because wasn't sure). You apply just asoc part right?
> Thanks for comments!
I applied everything, Ben has said he is very busy so it seemed easiest
to just merge the whole thing.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:26:37 +0000 [thread overview]
Message-ID: <20110311122637.GH1760@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTintYQ=qO3PALBL-bkiYKQFw0+JiW3=-oZmkRhZ1@mail.gmail.com>
On Fri, Mar 11, 2011 at 01:23:37PM +0100, Belisko Marek wrote:
> You're right. I think sending whole patch to help understand what
> I'm trying to do (because wasn't sure). You apply just asoc part right?
> Thanks for comments!
I applied everything, Ben has said he is very busy so it seemed easiest
to just merge the whole thing.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: ben-linux@fluff.org, perex@perex.cz, tiwai@suse.de,
lrg@slimlogic.co.uk, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:26:37 +0000 [thread overview]
Message-ID: <20110311122637.GH1760@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTintYQ=qO3PALBL-bkiYKQFw0+JiW3=-oZmkRhZ1@mail.gmail.com>
On Fri, Mar 11, 2011 at 01:23:37PM +0100, Belisko Marek wrote:
> You're right. I think sending whole patch to help understand what
> I'm trying to do (because wasn't sure). You apply just asoc part right?
> Thanks for comments!
I applied everything, Ben has said he is very busy so it seemed easiest
to just merge the whole thing.
next prev parent reply other threads:[~2011-03-11 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 20:46 [PATCH RFC] arm: mini2440: Fix uda134x codec problem Marek Belisko
2011-03-09 20:46 ` Marek Belisko
2011-03-11 12:14 ` Liam Girdwood
2011-03-11 12:14 ` Liam Girdwood
2011-03-11 12:14 ` Liam Girdwood
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:23 ` Belisko Marek
2011-03-11 12:23 ` Belisko Marek
2011-03-11 12:26 ` Mark Brown [this message]
2011-03-11 12:26 ` Mark Brown
2011-03-11 12:26 ` Mark Brown
2011-03-21 23:17 ` Ben Dooks
2011-03-21 23:17 ` Ben Dooks
2011-03-21 23:17 ` Ben Dooks
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=20110311122637.GH1760@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=marek.belisko@gmail.com \
--cc=tiwai@suse.de \
/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.