From: George Cherian <gcherian@caviumnetworks.com>
To: Christoph Hellwig <hch@lst.de>,
George Cherian <george.cherian@cavium.com>
Cc: David Daney <david.daney@cavium.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: crypto/cavium MSI-X fixups
Date: Wed, 15 Feb 2017 14:47:09 +0530 [thread overview]
Message-ID: <58A41C95.2090408@caviumnetworks.com> (raw)
In-Reply-To: <20170215071843.30108-1-hch@lst.de>
Hi Christoph,
On 02/15/2017 12:48 PM, Christoph Hellwig wrote:
> Hi George,
>
> your commit "crypto: cavium - Add Support for Octeon-tx CPT Engine"
> add a new caller to pci_enable_msix. This API has long been deprecated
> so this series switches it to use pci_alloc_irq_vectors instead.
>
> Can you please test it and make sure it goes in before the end of the
> merge window so that no more users of the old API hit mainline?
Yes the changes works well.
Acked-by: George Cherian <george.cherian@cavium.com>
for the series.
>
next prev parent reply other threads:[~2017-02-15 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 7:18 crypto/cavium MSI-X fixups Christoph Hellwig
2017-02-15 7:18 ` [PATCH 1/3] crypto: cavium: remove dead MSI-X related define Christoph Hellwig
2017-02-15 7:18 ` [PATCH 2/3] crypto: cavium/cptpf: switch to pci_alloc_irq_vectors Christoph Hellwig
2017-02-15 7:18 ` [PATCH 3/3] crypto: cavium/cptvf: " Christoph Hellwig
2017-02-15 9:17 ` George Cherian [this message]
2017-02-19 17:32 ` crypto/cavium MSI-X fixups Christoph Hellwig
2017-02-21 17:36 ` David Daney
2017-02-22 7:27 ` Christoph Hellwig
2017-02-22 17:45 ` David Daney
2017-02-23 12:16 ` Herbert Xu
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=58A41C95.2090408@caviumnetworks.com \
--to=gcherian@caviumnetworks.com \
--cc=david.daney@cavium.com \
--cc=george.cherian@cavium.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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 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).