linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Piotr Jaroszynski <pjaroszynski@nvidia.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	KY Srinivasan <kys@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>,
	"driverdev-devel@linuxdriverproject.org"
	<driverdev-devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain
Date: Thu, 20 Apr 2017 12:12:12 -0700	[thread overview]
Message-ID: <20170420191212.GA25415@infradead.org> (raw)
In-Reply-To: <BLUPR03MB1412F7A0A693B67685D5FE9FCA1B0@BLUPR03MB1412.namprd03.prod.outlook.com>

On Thu, Apr 20, 2017 at 06:37:35PM +0000, Haiyang Zhang wrote:
> It's Nvidia driver.

Which of the many nvidia drivers in the tree?  Just fix it instead of
coming up with stupid workarounds like this.

  reply	other threads:[~2017-04-20 19:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 16:35 [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain Haiyang Zhang
2017-04-20 18:33 ` Bjorn Helgaas
2017-04-20 18:37   ` Haiyang Zhang
2017-04-20 19:12     ` Christoph Hellwig [this message]
2017-04-24 23:06     ` John Hubbard
2017-04-25 13:00       ` Dan Carpenter
2017-04-25 13:14       ` Christoph Hellwig
2017-04-25 18:19         ` John Hubbard
  -- strict thread matches above, loose matches on Subject: below --
2017-05-24 20:39 Haiyang Zhang
2017-05-24 20:43 ` Haiyang Zhang
     [not found]   ` <20170525141955.6cee8fbb@alans-desktop>
2017-05-25 15:52     ` Stephen Hemminger
2017-05-25  7:56 ` Christoph Hellwig
2017-06-19 21:07 ` Bjorn Helgaas
2017-06-19 21:10   ` Christoph Hellwig

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=20170420191212.GA25415@infradead.org \
    --to=hch@infradead.org \
    --cc=bhelgaas@google.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=pjaroszynski@nvidia.com \
    --cc=sthemmin@microsoft.com \
    --cc=vkuznets@redhat.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).