From: Vasily khoruzhick <anarsoul@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Ben Dooks <ben-linux@fluff.org>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH RESEND v3 1/1] ASoC: Add HP iPAQ H1940 support
Date: Fri, 15 Oct 2010 15:52:41 +0300 [thread overview]
Message-ID: <20101015155241.73a34753@gmail.com> (raw)
In-Reply-To: <20101015113738.GJ14782@rakim.wolfsonmicro.main>
[-- Attachment #1.1: Type: text/plain, Size: 734 bytes --]
On Fri, 15 Oct 2010 12:37:38 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Fri, Oct 15, 2010 at 10:49:27AM +0300, Vasily khoruzhick wrote:
>
> > Dependencies was merged into linux-next tonight, so I suspect this
> > patch can be merged if you pull from linux-next.
>
> -next is an integration tree which should never be merged into other
> trees. I really need either Linus' tree or a specific branch I can
> merge into ASoC.
It's next-samsung from Ben's tree
(git://git.fluff.org/bjdooks/linux.git), I suspect it will be merged into
Linus' tree during 2.6.37 merge window, not sure if it's safe/ok to merge it
into ASoC right now. Let's wait for 2.6.37 merge window then.
Regards
Vasily
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-10-15 12:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 10:55 [PATCH] ASoC: Add HP iPAQ H1940 support Vasily Khoruzhick
2010-09-12 12:14 ` Jassi Brar
2010-09-12 12:15 ` Vasily Khoruzhick
2010-09-12 12:18 ` [PATCH v2 0/1] " Vasily Khoruzhick
2010-09-12 12:18 ` [PATCH v2 1/1] " Vasily Khoruzhick
2010-09-12 13:25 ` Marek Vasut
2010-09-12 17:07 ` Jassi Brar
2010-09-12 18:09 ` Vasily Khoruzhick
2010-09-13 1:09 ` Jassi Brar
2010-09-13 9:05 ` Mark Brown
2010-09-13 9:12 ` Vasily Khoruzhick
2010-09-13 9:47 ` [PATCH v3 0/1] " Vasily Khoruzhick
2010-09-13 9:47 ` [PATCH v3 1/1] " Vasily Khoruzhick
2010-09-20 10:38 ` Mark Brown
2010-09-27 7:47 ` [PATCH RESEND " Vasily Khoruzhick
2010-09-27 15:06 ` Mark Brown
2010-09-27 15:29 ` Vasily Khoruzhick
2010-10-15 7:49 ` Vasily khoruzhick
2010-10-15 11:37 ` Mark Brown
2010-10-15 12:52 ` Vasily khoruzhick [this message]
2010-09-13 9:07 ` [PATCH v2 " 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=20101015155241.73a34753@gmail.com \
--to=anarsoul@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.patard@rtp-net.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.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.