From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd_soc_dai_link.init()
Date: Fri, 01 Jun 2007 15:41:20 +0100 [thread overview]
Message-ID: <1180708880.26032.79.camel@localhost.localdomain> (raw)
In-Reply-To: <1180705118.26032.72.camel@localhost.localdomain>
On Fri, 2007-06-01 at 14:38 +0100, Liam Girdwood wrote:
> On Thu, 2007-05-31 at 18:14 -0500, Timur Tabi wrote:
> > 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.
> >
> >
> >
>
> Sorry, we've just added http support now.
>
> I'm going to create a new branch off dev called ppc-dev (will be visible
> in a few hours). This will be the best place for ppc dev.
http:// URL is :-
git-clone http://opensource.wolfsonmicro.com/~git/linux-2.6-asoc/
This will be pull/clone access only. I've created a separate ppc-dev
(will show up in a few hours) branch as it will be easier to merge
changes in without affecting any of the current working dev tree for
other platforms.
I'm going to move the I2C probing out of a codec driver tonight.
Liam
next prev parent reply other threads:[~2007-06-01 14:41 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 ` snd_soc_dai_link.init() Timur Tabi
2007-06-01 13:38 ` snd_soc_dai_link.init() Liam Girdwood
2007-06-01 14:41 ` Liam Girdwood [this message]
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=1180708880.26032.79.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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).