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-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nsekhar@ti.com,
tony@atomide.com
Subject: Re: [PATCH] dmaengine: edma: Fix paRAM slot allocation for entry channel 0
Date: Wed, 13 Jan 2016 19:09:51 +0530 [thread overview]
Message-ID: <20160113133951.GG11130@localhost> (raw)
In-Reply-To: <1452501481-5543-1-git-send-email-peter.ujfalusi@ti.com>
On Mon, Jan 11, 2016 at 10:38:01AM +0200, Peter Ujfalusi wrote:
> edma_alloc_slot was not checking the channel mapping support existence when
> slot 0 has been requested (used as entry slot for channel/event 0).
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-01-13 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 8:38 [PATCH] dmaengine: edma: Fix paRAM slot allocation for entry channel 0 Peter Ujfalusi
2016-01-13 13:39 ` 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=20160113133951.GG11130@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--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).