From: Vinod Koul <vkoul@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Peng Ma <peng.ma@nxp.com>, Wen He <wen.he_1@nxp.com>,
Jiaheng Fan <jiaheng.fan@nxp.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT] dmaengine: fsl-qdma: Handle invalid qdma-queue0 IRQ
Date: Sat, 2 Nov 2019 21:56:06 +0530 [thread overview]
Message-ID: <20191102162606.GC2695@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20191004150826.6656-1-krzk@kernel.org>
On 04-10-19, 17:08, Krzysztof Kozlowski wrote:
> platform_get_irq_byname() might return -errno which later would be cast
> to an unsigned int and used in IRQ handling code leading to usage of
> wrong ID and errors about wrong irq_base.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-11-02 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 15:08 [RFT] dmaengine: fsl-qdma: Handle invalid qdma-queue0 IRQ Krzysztof Kozlowski
2019-10-21 9:54 ` [EXT] " Peng Ma
2019-11-02 16:26 ` 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=20191102162606.GC2695@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jiaheng.fan@nxp.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.ma@nxp.com \
--cc=wen.he_1@nxp.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).