From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vladimir Zapolskiy <vzapolskiy@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2/2 v2] ASoC: uda134x: correct bias level setup for codecs family
Date: Wed, 30 Jun 2010 15:08:24 +0100 [thread overview]
Message-ID: <20100630140824.GD3634@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTil63jxubLbilJwuETe_g_tSbUoxmmaAh01z2VPA@mail.gmail.com>
On Wed, Jun 30, 2010 at 05:10:52PM +0400, Vladimir Zapolskiy wrote:
> Anyhow in broonie/sound-2.6 tree, branch `for-2.6.36' I can't find applied
> all 4 sent patches recently, e.g. 2 patchsets with 2 patches each, only
> the second patchset was applied 5 days ago.
> Probably I look at invalid branch?
You need to allow at least a few minutes for the kernel.org system to
mirror out the commits after I push them, and I tend to send these mails
as soon as I've applied locally rather than when I push stuff out.
next prev parent reply other threads:[~2010-06-30 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 11:17 [PATCH 1/2] ASoC: uda134x: add DATA011 register found in codecs family Vladimir Zapolskiy
2010-06-24 11:17 ` [PATCH 2/2] ASoC: uda134x: fix bias level setup on initialization and runtime Vladimir Zapolskiy
2010-06-24 11:34 ` Mark Brown
2010-06-24 13:21 ` Vladimir Zapolskiy
2010-06-24 13:19 ` [PATCH 2/2 v2] ASoC: uda134x: correct bias level setup for codecs family Vladimir Zapolskiy
2010-06-24 19:44 ` Vladimir Zapolskiy
2010-06-28 5:38 ` Vladimir Zapolskiy
2010-06-30 12:58 ` Mark Brown
2010-06-30 13:10 ` Vladimir Zapolskiy
2010-06-30 14:08 ` Mark Brown [this message]
2010-06-30 14:59 ` Vladimir Zapolskiy
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=20100630140824.GD3634@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=vzapolskiy@gmail.com \
/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).