From: Vinod Koul <vkoul@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: dmaengine@vger.kernel.org
Subject: [V2,1/3] dmaengine: dmatest: wrap src & dst data into a struct
Date: Mon, 25 Feb 2019 23:14:12 +0530 [thread overview]
Message-ID: <20190225174412.GK31146@vkoul-mobl> (raw)
On 12-02-19, 17:11, Alexandru Ardelean wrote:
> This change wraps the data for the source & destination buffers into a
> `struct dmatest_data`. The rename patterns are:
> * src_cnt -> src->cnt
> * dst_cnt -> dst->cnt
> * src_off -> src->off
> * dst_off -> dst->off
> * thread->srcs -> src->aligned
> * thread->usrcs -> src->raw
> * thread->dsts -> dst->aligned
> * thread->udsts -> dst->raw
>
> The intent is to make a function that moves duplicate parts of the code
> into common alloc & free functions, which will unclutter the
> `dmatest_func()` function.
Applied all 3, thanks
next reply other threads:[~2019-02-25 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 17:44 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 15:11 [V2,1/3] dmaengine: dmatest: wrap src & dst data into a struct Alexandru Ardelean
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=20190225174412.GK31146@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=dmaengine@vger.kernel.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