From: Timur Tabi <timur@freescale.com>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd_soc_dai_link.init()
Date: Thu, 31 May 2007 18:14:26 -0500 [thread overview]
Message-ID: <465F56D2.70201@freescale.com> (raw)
In-Reply-To: <1180631362.29590.90.camel@a10072.wolfsonmicro.main>
Liam Girdwood wrote:
> http://opensource.wolfsonmicro.com/cgi-bin/gitweb/gitweb.cgi?p=linux-2.6-asoc;a=summary
>
> Master branch should be up to date with mainline, for-alsa-kernel branch
> should be close to alsa-kernel Hg.
Does the http:// protocol work with your git repo? Our corporate firewall doesn't allow
the git:// protocol.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-31 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 22:34 snd_soc_dai_link.init() Timur Tabi
2007-05-31 17:02 ` snd_soc_dai_link.init() Liam Girdwood
2007-05-31 17:04 ` snd_soc_dai_link.init() Timur Tabi
2007-05-31 17:09 ` snd_soc_dai_link.init() Liam Girdwood
2007-05-31 23:14 ` Timur Tabi [this message]
2007-06-01 13:38 ` snd_soc_dai_link.init() Liam Girdwood
2007-06-01 14:41 ` snd_soc_dai_link.init() Liam Girdwood
2007-06-01 16:42 ` snd_soc_dai_link.init() Timur Tabi
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=465F56D2.70201@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=lg@opensource.wolfsonmicro.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).