From: Vinod Koul <vinod.koul@intel.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
dan.j.williams@intel.com, lars@metafoo.de
Subject: [v3] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED
Date: Wed, 2 May 2018 10:07:23 +0530 [thread overview]
Message-ID: <20180502043722.GR6014@localhost> (raw)
On Sat, Apr 28, 2018 at 12:57:54PM -0700, Moritz Fischer wrote:
> Request IRQ with IRQF_SHARED flag to enable setups with multiple
> instances of the core sharing a single IRQ line.
> This works out since the IRQ handler already checks if there is
> an actual IRQ pending and returns IRQ_NONE otherwise.
Applied, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
dan.j.williams@intel.com, lars@metafoo.de
Subject: Re: [PATCH v3] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED
Date: Wed, 2 May 2018 10:07:23 +0530 [thread overview]
Message-ID: <20180502043722.GR6014@localhost> (raw)
In-Reply-To: <20180428195754.3053-1-mdf@kernel.org>
On Sat, Apr 28, 2018 at 12:57:54PM -0700, Moritz Fischer wrote:
> Request IRQ with IRQF_SHARED flag to enable setups with multiple
> instances of the core sharing a single IRQ line.
> This works out since the IRQ handler already checks if there is
> an actual IRQ pending and returns IRQ_NONE otherwise.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-05-02 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 4:37 Vinod Koul [this message]
2018-05-02 4:37 ` [PATCH v3] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-04-28 19:57 [v3] " mdf
2018-04-28 19:57 ` [PATCH v3] " Moritz Fischer
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=20180502043722.GR6014@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.