From: Timur Tabi <timur@freescale.com>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASOC: Best way to get private data from machine driver to the other drivers?
Date: Mon, 01 Oct 2007 15:10:46 -0500 [thread overview]
Message-ID: <47015446.9010707@freescale.com> (raw)
In-Reply-To: <1191236021.3318.41.camel@localhost.localdomain>
Liam Girdwood wrote:
> Could you have a look at the V2 i.mx31 SSI driver and let me know if we
> need further changes for better dts support.
I'll do that. However, I still have the same problem - without a git-http
interface, my ability to "work with" that repository is limited. Can you
create a repo on kernel.org? I have git better access to that site.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-10-01 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 21:14 ASOC: Best way to get private data from machine driver to the other drivers? Timur Tabi
2007-10-01 10:53 ` Liam Girdwood
2007-10-01 20:10 ` Timur Tabi [this message]
2007-10-02 16:40 ` Liam Girdwood
2007-10-02 16:49 ` Timur Tabi
2007-10-02 16:50 ` Timur Tabi
2007-10-01 21:49 ` Timur Tabi
2007-10-02 16:37 ` Liam Girdwood
2007-10-02 16:48 ` 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=47015446.9010707@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