From: Huang Shijie <b32955@freescale.com>
To: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
"LW@KARO-electronics.de" <LW@KARO-electronics.de>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>, "lrg@ti.com" <lrg@ti.com>,
"cjb@laptop.org" <cjb@laptop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/2] patch set about the MXS-DMA
Date: Wed, 29 Feb 2012 16:25:09 +0800 [thread overview]
Message-ID: <4F4DE0E5.8070808@freescale.com> (raw)
In-Reply-To: <1330502098.3545.78.camel@sauron.fi.intel.com>
Hi Artem:
> On Wed, 2012-02-29 at 11:10 +0800, Huang Shijie wrote:
>> Hi:
>>
>> ping.
> Is this patch-set independent or requires something like gpma patches?
>
This patch set is independent, and it does not depend upon any other
patches.
I will sent out the new GPMI patches (with DT enable) after this
patch-set is merged.
thanks
BR
Huang Shijie
WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <b32955@freescale.com>
To: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"cjb@laptop.org" <cjb@laptop.org>,
"Koul, Vinod" <vinod.koul@intel.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"lrg@ti.com" <lrg@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"LW@KARO-electronics.de" <LW@KARO-electronics.de>
Subject: Re: [PATCH v6 0/2] patch set about the MXS-DMA
Date: Wed, 29 Feb 2012 16:25:09 +0800 [thread overview]
Message-ID: <4F4DE0E5.8070808@freescale.com> (raw)
In-Reply-To: <1330502098.3545.78.camel@sauron.fi.intel.com>
Hi Artem:
> On Wed, 2012-02-29 at 11:10 +0800, Huang Shijie wrote:
>> Hi:
>>
>> ping.
> Is this patch-set independent or requires something like gpma patches?
>
This patch set is independent, and it does not depend upon any other
patches.
I will sent out the new GPMI patches (with DT enable) after this
patch-set is merged.
thanks
BR
Huang Shijie
WARNING: multiple messages have this Message-ID (diff)
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/2] patch set about the MXS-DMA
Date: Wed, 29 Feb 2012 16:25:09 +0800 [thread overview]
Message-ID: <4F4DE0E5.8070808@freescale.com> (raw)
In-Reply-To: <1330502098.3545.78.camel@sauron.fi.intel.com>
Hi Artem:
> On Wed, 2012-02-29 at 11:10 +0800, Huang Shijie wrote:
>> Hi:
>>
>> ping.
> Is this patch-set independent or requires something like gpma patches?
>
This patch set is independent, and it does not depend upon any other
patches.
I will sent out the new GPMI patches (with DT enable) after this
patch-set is merged.
thanks
BR
Huang Shijie
next prev parent reply other threads:[~2012-02-29 8:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 6:17 [PATCH v6 0/2] patch set about the MXS-DMA Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` [PATCH v6 1/2] mxs-dma : move the mxs dma.h to a more common place Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` [PATCH v6 2/2] mxs-dma : rewrite the last parameter of mxs_dma_prep_slave_sg() Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-16 6:17 ` Huang Shijie
2012-02-29 3:10 ` [PATCH v6 0/2] patch set about the MXS-DMA Huang Shijie
2012-02-29 3:10 ` Huang Shijie
2012-02-29 3:10 ` Huang Shijie
2012-02-29 3:10 ` Huang Shijie
2012-02-29 7:52 ` Bityutskiy, Artem
2012-02-29 7:52 ` Bityutskiy, Artem
2012-02-29 7:52 ` Bityutskiy, Artem
2012-02-29 8:25 ` Huang Shijie [this message]
2012-02-29 8:25 ` Huang Shijie
2012-02-29 8:25 ` Huang Shijie
2012-02-29 12:00 ` Bityutskiy, Artem
2012-02-29 12:00 ` Bityutskiy, Artem
2012-02-29 12:00 ` Bityutskiy, Artem
2012-02-29 13:13 ` Huang Shijie
2012-02-29 13:13 ` Huang Shijie
2012-02-29 13:13 ` Huang Shijie
2012-03-02 20:50 ` Chris Ball
2012-03-02 20:50 ` Chris Ball
2012-03-02 20:50 ` Chris Ball
2012-03-02 20:50 ` Chris Ball
2012-03-03 1:54 ` Huang Shijie
2012-03-03 1:54 ` Huang Shijie
2012-03-03 1:54 ` Huang Shijie
2012-03-03 1:54 ` Huang Shijie
2012-03-05 4:47 ` Vinod Koul
2012-03-05 4:47 ` Vinod Koul
2012-03-05 4:47 ` Vinod Koul
2012-03-19 20:44 ` Subodh Nijsure
2012-03-20 6:56 ` Artem Bityutskiy
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=4F4DE0E5.8070808@freescale.com \
--to=b32955@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=alsa-devel@alsa-project.org \
--cc=artem.bityutskiy@intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lrg@ti.com \
--cc=shawn.guo@linaro.org \
--cc=vinod.koul@intel.com \
--cc=w.sang@pengutronix.de \
/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.