From: Christoph Hellwig <hch@lst.de>
To: dev.srinivasulu@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, sgoutham@cavium.com,
tsrinivasulu@cavium.com, hch@lst.de
Subject: Re: [PATCH] net: thunderx: Switch to pci_alloc_irq_vectors
Date: Wed, 5 Apr 2017 08:27:40 +0200 [thread overview]
Message-ID: <20170405062740.GB26470@lst.de> (raw)
In-Reply-To: <1491298146-13609-1-git-send-email-tsrinivasulu@cavium.com>
On Tue, Apr 04, 2017 at 02:59:06PM +0530, dev.srinivasulu@gmail.com wrote:
> From: Thanneeru Srinivasulu <tsrinivasulu@cavium.com>
>
> Remove deprecated pci_enable_msix API in favour of it's
> successor pci_alloc_irq_vectors.
>
> Signed-off-by: Thanneeru Srinivasulu <tsrinivasulu@cavium.com>
> Signed-off-by: Sunil Goutham <sgoutham@cavium.com>
Looks good.
Are you fine with me queueing this up together with the other
pci_enable_msix() removal patches?
next prev parent reply other threads:[~2017-04-05 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 9:29 [PATCH] net: thunderx: Switch to pci_alloc_irq_vectors dev.srinivasulu
2017-04-05 6:27 ` Christoph Hellwig [this message]
2017-04-05 6:37 ` Thanneeru Srinivasulu
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=20170405062740.GB26470@lst.de \
--to=hch@lst.de \
--cc=dev.srinivasulu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@cavium.com \
--cc=tsrinivasulu@cavium.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).