From: Vinod Koul <vkoul@kernel.org>
To: Piotr Stankiewicz <piotr.stankiewicz@intel.com>
Cc: Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/15] dmaengine: dw-edma: use PCI_IRQ_MSI_TYPES where appropriate
Date: Tue, 16 Jun 2020 23:41:44 +0530 [thread overview]
Message-ID: <20200616181144.GQ2324254@vkoul-mobl> (raw)
In-Reply-To: <20200616163104.GN2324254@vkoul-mobl>
On 16-06-20, 22:01, Vinod Koul wrote:
> On 02-06-20, 11:20, Piotr Stankiewicz wrote:
> > Seeing as there is shorthand available to use when asking for any type
> > of interrupt, or any type of message signalled interrupt, leverage it.
>
> Applied, thanks
Dropped now.. PCI_IRQ_MSI_TYPES is not upstream yet!
Feel free to take in PCI tree with my ack
Acked-By: Vinod Koul <vkoul@kernel.org>
--
~Vinod
prev parent reply other threads:[~2020-06-16 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 9:20 [PATCH 06/15] dmaengine: dw-edma: use PCI_IRQ_MSI_TYPES where appropriate Piotr Stankiewicz
2020-06-16 16:31 ` Vinod Koul
2020-06-16 18:11 ` 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=20200616181144.GQ2324254@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr.stankiewicz@intel.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).