From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dmaengine: hdmac: factorise memset descriptor allocation
Date: Fri, 9 Oct 2015 16:29:27 +0100 [thread overview]
Message-ID: <20151009152926.GD3609@vkoul-mobl.iind.intel.com> (raw)
In-Reply-To: <20151007173317.GG2278@lukather>
On Wed, Oct 07, 2015 at 06:33:17PM +0100, Maxime Ripard wrote:
> > This is fine, but this is driver limitation. We should really split the
> > txn to multiple descriptors here..
>
> Both these things are actually just copy from the previous code.
>
> I can probably fix the first style issue in this patch, but splitting
> the memset descriptors should go in a separate patch.
That sounds fine
--
~Vinod
next prev parent reply other threads:[~2015-10-09 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 14:52 [PATCH 0/2] dmaengine: hdmac: Add scatter-gathered memset support Maxime Ripard
2015-10-01 14:52 ` [PATCH 1/2] dmaengine: hdmac: factorise memset descriptor allocation Maxime Ripard
2015-10-07 13:54 ` Vinod Koul
2015-10-07 17:33 ` Maxime Ripard
2015-10-09 15:29 ` Vinod Koul [this message]
2015-10-01 14:52 ` [PATCH 2/2] dmaengine: hdmac: Add scatter-gathered memset support Maxime Ripard
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=20151009152926.GD3609@vkoul-mobl.iind.intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@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