From: Vinod Koul <vkoul@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: dmaengine@vger.kernel.org
Subject: dmaengine: dmatest: move size checks earlier in function
Date: Sat, 24 Nov 2018 19:21:32 +0530 [thread overview]
Message-ID: <20181124135132.GF3175@vkoul-mobl.Dlink> (raw)
On 01-11-18, 18:07, Alexandru Ardelean wrote:
> There's no need to allocate all that memory if these sizes are invalid
> anyway.
Applied, thanks
next reply other threads:[~2018-11-24 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 13:51 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-01 16:07 dmaengine: dmatest: move size checks earlier in function 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=20181124135132.GF3175@vkoul-mobl.Dlink \
--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