From: Subodh Nijsure <snijsure@grid-net.com>
To: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
Cc: Huang Shijie <b32955@freescale.com>, mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v6 0/2] patch set about the MXS-DMA
Date: Mon, 19 Mar 2012 13:44:27 -0700 [thread overview]
Message-ID: <4F679AAB.6030506@grid-net.com> (raw)
In-Reply-To: <1330516974.3545.104.camel@sauron.fi.intel.com>
On 02/29/2012 04:00 AM, Bityutskiy, Artem wrote:
> On Wed, 2012-02-29 at 16:25 +0800, Huang Shijie wrote:
>> 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.
> Pushed both to l2-mtd.git tree, thanks. I am worried that it touches
> other subsystems like dma, sound, and mmc and there are no acks for
> those. Would be nice to get them somehow.
I am using following git
git remote -v
origin git://git.infradead.org/mtd-2.6.git (fetch)
origin git://git.infradead.org/mtd-2.6.git (push)
And I don't see MXS-DMA patch applied, am I looking at the wrong
tree/branch for l2-mtd.git? Or this patch not applied to l2-mtd.git tree?
/Subodh
next prev parent reply other threads:[~2012-03-19 20:44 UTC|newest]
Thread overview: 13+ 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 ` [PATCH v6 1/2] mxs-dma : move the mxs dma.h to a more common place 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-29 3:10 ` [PATCH v6 0/2] patch set about the MXS-DMA Huang Shijie
2012-02-29 7:52 ` Bityutskiy, Artem
2012-02-29 8:25 ` Huang Shijie
2012-02-29 12:00 ` Bityutskiy, Artem
2012-02-29 13:13 ` Huang Shijie
2012-03-02 20:50 ` Chris Ball
2012-03-03 1:54 ` Huang Shijie
2012-03-05 4:47 ` Vinod Koul
2012-03-19 20:44 ` Subodh Nijsure [this message]
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=4F679AAB.6030506@grid-net.com \
--to=snijsure@grid-net.com \
--cc=artem.bityutskiy@intel.com \
--cc=b32955@freescale.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox