From: Huang Shijie <b32955@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: <vinod.koul@intel.com>, <artem.bityutskiy@intel.com>,
<w.sang@pengutronix.de>, <LW@KARO-electronics.de>,
<broonie@opensource.wolfsonmicro.com>, <lrg@ti.com>,
<cjb@laptop.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-mtd@lists.infradead.org>, <linux-mmc@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 2/2] mxs-dma : rewrite the last parameter of mxs_dma_prep_slave_sg()
Date: Thu, 16 Feb 2012 10:27:34 +0800 [thread overview]
Message-ID: <4F3C6996.8060205@freescale.com> (raw)
In-Reply-To: <20120216021223.GF30946@r65073-Latitude-D630>
Hi,
>> Hi Shawn:
>>> I'm trying to give it a test. But it does not apply on either mainline
>>> or next tree. You probably had a wrong base for this patch.
>>>
>> thanks for your work.
>>
>> As the previous email said, this patch set bases on :[PATCH v2]
>> mtd/gpmi : add gpmi support for mx6q.
>>
> Then you are doing something wrong. This series should be based on
> mainline, and then you add imx6q support on top of this series.
sorry for the inconvenience.
I send the two patches at the same time.
The mtd/gpmi patch is just a small patch, I think it will be merged
before this patch set.
BR
Huang Shijie
prev parent reply other threads:[~2012-02-16 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:25 [PATCH v5 0/2] patch set about the MXS-DMA Huang Shijie
2012-02-13 5:25 ` [PATCH v5 1/2] mxs-dma : move the mxs dma.h to a more common place Huang Shijie
2012-02-13 16:33 ` Mark Brown
2012-02-15 19:56 ` Shawn Guo
2012-02-13 5:25 ` [PATCH v5 2/2] mxs-dma : rewrite the last parameter of mxs_dma_prep_slave_sg() Huang Shijie
2012-02-15 19:55 ` Shawn Guo
2012-02-16 2:05 ` Huang Shijie
2012-02-16 2:12 ` Shawn Guo
2012-02-16 2:27 ` Huang Shijie [this message]
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=4F3C6996.8060205@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 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).