From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@arm.linux.org.uk,
linux-omap@vger.kernel.org, tony@atomide.com
Subject: Re: [PATCH] dma: omap-dma: Implement device_slave_caps callback
Date: Sat, 29 Mar 2014 19:06:22 +0530 [thread overview]
Message-ID: <20140329133622.GP1976@intel.com> (raw)
In-Reply-To: <1394199404-7870-1-git-send-email-peter.ujfalusi@ti.com>
On Fri, Mar 07, 2014 at 03:36:44PM +0200, Peter Ujfalusi wrote:
> With the callback implemented omap-dma can provide information to client
> drivers regarding to supported address widths, directions, residue
> granularity, etc.
>
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2014-03-29 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:36 [PATCH] dma: omap-dma: Implement device_slave_caps callback Peter Ujfalusi
2014-03-12 17:37 ` Tony Lindgren
2014-03-13 7:48 ` Peter Ujfalusi
2014-03-13 16:25 ` Tony Lindgren
2014-03-29 13:36 ` Vinod Koul [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=20140329133622.GP1976@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).