From: Eric Miao <eric.y.miao@gmail.com>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] Update Poodle to current ASoC API
Date: Thu, 24 Jul 2008 21:38:19 +0800 [thread overview]
Message-ID: <488885CB.702@gmail.com> (raw)
In-Reply-To: <20080724131019.GA14962@sirena.org.uk>
Mark Brown wrote:
> On Thu, Jul 24, 2008 at 04:54:48PM +0400, Dmitry Baryshkov wrote:
>> Signed-off-by: Dmitry Baryshkov <dbaryshkov@gmail.com>
>> Cc: Richard Purdie <rpurdie@rpsys.net>
>> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
>> ---
>> This should probably go into 2.6.27, if possible
>
> I've queued this for Takashi, thanks (he's on holiday this week). I
> had thought that at least the second hunk was already fixed but it seems
> not.
>
This probably should go through the arm tree, along with other
poodle patches, otherwise it just creates headache for Russell
in the next merge.
As if should go into 2.6.27, I don't know. Depending on if it
qualifies to be a fix or just a clean-up, from ALSA's point of
view.
> Please CC all ALSA patches to alsa-devel@alsa-project.org.
>
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2008-07-24 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080724125448.GA4695@doriath.ww600.siemens.net>
2008-07-24 13:10 ` [PATCH 2/2] Update Poodle to current ASoC API Mark Brown
2008-07-24 13:13 ` Dmitry Baryshkov
2008-07-24 13:36 ` Mark Brown
2008-07-24 13:38 ` Eric Miao [this message]
2008-07-24 13:44 ` Dmitry Baryshkov
2008-07-24 14:03 ` Mark Brown
2008-07-24 15:07 ` 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=488885CB.702@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
/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.