From: Christoph Hellwig <hch@infradead.org>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-nvme@lists.infradead.org, sagi@grimberg.me,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 01/17] lpfc: Use new pci_alloc_irq_vectors() interface
Date: Wed, 18 Jan 2017 08:54:43 -0800 [thread overview]
Message-ID: <20170118165443.GA14012@infradead.org> (raw)
In-Reply-To: <587ec2ec.lHOM16QZ9nmppg4/%jsmart2021@gmail.com>
On Tue, Jan 17, 2017 at 05:20:44PM -0800, James Smart wrote:
>
> Move to new pci_alloc_irq_vectors() interface for intx/msi/msix
>
> Note: io channel paradigm remains, for now.
Not exactly a well written changelog. I'd like to know why this is
better than my version here:
http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/lpfc-msix
It also seems to be missing the post_vectors setting for the
Flash Optimized Fabric interrupt, which may lead to an incorrect
vector assignment for all the queues.
next prev parent reply other threads:[~2017-01-18 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:20 [PATCH 01/17] lpfc: Use new pci_alloc_irq_vectors() interface James Smart
2017-01-18 6:57 ` Hannes Reinecke
2017-01-18 16:54 ` Christoph Hellwig [this message]
2017-01-19 4:57 ` James Smart
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=20170118165443.GA14012@infradead.org \
--to=hch@infradead.org \
--cc=jsmart2021@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sagi@grimberg.me \
/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