From: Dmitry Baryshkov <dbaryshkov@gmail.com>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] Permit simultaneous compilation of both PXA AC97 drivers
Date: Mon, 08 Sep 2008 14:19:13 +0400 [thread overview]
Message-ID: <48C4FC21.3060107@gmail.com> (raw)
In-Reply-To: <20080908093047.GA790@sirena.org.uk>
Mark Brown wrote:
> On Mon, Sep 08, 2008 at 01:06:09PM +0400, Dmitry Baryshkov wrote:
>> Signed-off-by: Dmitry Baryshkov <dbaryshkov@gmail.com>
>
> This change was merged some time ago - it's easier if you development
> against Takashi's tree rather than against an old kernel, especially
> given the changes going on in ASoC. I haven't checked yet but I expect
> that some of your later changes will no longer apply with current code.
Against which tree should I develop?
git://opensource.wolfsonmicro.com/linux-2.6-asoc ?
--
With best wishes
Dmitry
next prev parent reply other threads:[~2008-09-08 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 8:53 [GIT PULL] unify two pxa sound drivers Dmitry Baryshkov
2008-09-08 9:05 ` Liam Girdwood
2008-09-08 9:06 ` [PATCH 1/5] Permit simultaneous compilation of both PXA AC97 drivers Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 2/5] Separate common pxa2xx-ac97 code Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 3/5] Make pxa-ac97-lib separate module Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 4/5] pxa2xx-lib: support building for several pxa's Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 5/5] Separate common pxa2xx-pcm code Dmitry Baryshkov
2008-09-08 10:07 ` Eric Miao
2008-09-08 10:13 ` Dmitry
2008-09-08 10:33 ` Mark Brown
2008-09-08 10:17 ` [PATCH 4/5] pxa2xx-lib: support building for several pxa's Mark Brown
2008-09-08 9:33 ` [PATCH 2/5] Separate common pxa2xx-ac97 code Liam Girdwood
2008-09-08 9:42 ` Dmitry Baryshkov
2008-09-08 9:51 ` Liam Girdwood
2008-09-08 9:30 ` [PATCH 1/5] Permit simultaneous compilation of both PXA AC97 drivers Mark Brown
2008-09-08 10:19 ` Dmitry Baryshkov [this message]
2008-09-08 10:35 ` Mark Brown
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=48C4FC21.3060107@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=alsa-devel@alsa-project.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 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.