Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Martin Mares <mj@ucw.cz>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCH] pciutils: Add support for 32-bit PCI domains
Date: Mon, 16 May 2016 11:44:10 -0400	[thread overview]
Message-ID: <20160516154409.GB10776@localhost.localdomain> (raw)
In-Reply-To: <mj+md-20160514.095828.61188.camelot@ucw.cz>

On Sat, May 14, 2016 at 11:59:55AM +0200, Martin Mares wrote:
> I have applied the patch and fixed a couple of minor problems. Most
> importantly, the 16-bit domain number was maintained in the sysfs back-end,
> so backward compatibility was not kept on other systems.
> 
> Could you please review the changes in pciutils.git?

Thanks for merging this in. Your changes look good to me, and tests
successfully on the h/w requiring it.

Thanks!

      reply	other threads:[~2016-05-16 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 19:19 [PATCH] pciutils: Add support for 32-bit PCI domains Keith Busch
2016-05-14  9:59 ` Martin Mares
2016-05-16 15:44   ` Keith Busch [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=20160516154409.GB10776@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=bhelgaas@google.com \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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