From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: zw@zh-kernel.org, Dan Williams <dan.j.williams@intel.com>,
Li Yang <leoli@freescale.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] fsl-dma: allow Freescale Elo DMA driver to be compiled as a module
Date: Wed, 24 Sep 2008 13:31:50 -0500 [thread overview]
Message-ID: <48DA8796.5020304@freescale.com> (raw)
In-Reply-To: <47B7FAA6-434C-440A-B55D-03C9882809CE@kernel.crashing.org>
Kumar Gala wrote:
> Dan, any update on this patch?
I'm going to post a new version. This whole thing is more complicated than I
thought.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Li Yang <leoli@freescale.com>,
zw@zh-kernel.org, linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fsl-dma: allow Freescale Elo DMA driver to be compiled as a module
Date: Wed, 24 Sep 2008 13:31:50 -0500 [thread overview]
Message-ID: <48DA8796.5020304@freescale.com> (raw)
In-Reply-To: <47B7FAA6-434C-440A-B55D-03C9882809CE@kernel.crashing.org>
Kumar Gala wrote:
> Dan, any update on this patch?
I'm going to post a new version. This whole thing is more complicated than I
thought.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-24 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 15:11 [PATCH] fsl-dma: allow Freescale Elo DMA driver to be compiled as a module Timur Tabi
2008-09-24 18:30 ` Kumar Gala
2008-09-24 18:30 ` Kumar Gala
2008-09-24 18:31 ` Timur Tabi [this message]
2008-09-24 18:31 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 16:24 Timur Tabi
2008-09-20 21:32 ` Dan Williams
2008-09-22 20:59 ` Timur Tabi
2008-09-23 20:46 ` Dan Williams
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=48DA8796.5020304@freescale.com \
--to=timur@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=galak@kernel.crashing.org \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=zw@zh-kernel.org \
/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.