From: Christoph Hellwig <hch@lst.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
agordeev@redhat.com, linux-pci@vger.kernel.org,
davem@davemloft.net, shane.huang@amd.com
Subject: Re: [PATCH, RFC] PCI: use pci_intx_for_msi in pci_alloc_irq_vectors
Date: Tue, 20 Sep 2016 22:03:10 +0200 [thread overview]
Message-ID: <20160920200310.GA768@lst.de> (raw)
In-Reply-To: <20160920194614.GE4941@localhost>
On Tue, Sep 20, 2016 at 02:46:14PM -0500, Bjorn Helgaas wrote:
> If we want to do this, I'd like to have a changelog that explains
> *why*, so I'm ignoring it for now. I'm not nacking it; I just don't
> understand why we should do it yet, and I'm too lazy to do all the
> research myself.
Can't blame you. Alex pointed me to the function, and it seems like a
good idea, but research in git history just doesn't give me an conclusive
reason on why to do it either.
prev parent reply other threads:[~2016-09-20 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 7:09 [PATCH, RFC] PCI: use pci_intx_for_msi in pci_alloc_irq_vectors Christoph Hellwig
2016-09-20 19:46 ` Bjorn Helgaas
2016-09-20 20:03 ` Christoph Hellwig [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=20160920200310.GA768@lst.de \
--to=hch@lst.de \
--cc=agordeev@redhat.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shane.huang@amd.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).