From: Vinod Koul <vinod.koul@intel.com>
To: Stefan Agner <stefan@agner.ch>
Cc: jingchang.lu@freescale.com, dan.j.williams@intel.com,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: fsl-edma: clear pending interrupts on initialization
Date: Fri, 12 Jun 2015 18:31:34 +0530 [thread overview]
Message-ID: <20150612130134.GK28601@localhost> (raw)
In-Reply-To: <1433706370-3867-1-git-send-email-stefan@agner.ch>
On Sun, Jun 07, 2015 at 09:46:10PM +0200, Stefan Agner wrote:
> Clear pending interrupts before requesting interrupts and move
> interrupt initialization after channels have been initialized.
> This avoids a NULL pointer dereference panic when using kexec
> while DMA requests were running.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2015-06-12 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 19:46 [PATCH] dmaengine: fsl-edma: clear pending interrupts on initialization Stefan Agner
2015-06-12 13:01 ` 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=20150612130134.GK28601@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jingchang.lu@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@agner.ch \
/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