From: David Miller <davem@davemloft.net>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, sparclinux@vger.kernel.org,
dan.yeisley@unisys.com, yinghai@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases()
Date: Mon, 09 Jul 2012 14:25:31 -0700 (PDT) [thread overview]
Message-ID: <20120709.142531.1530660875837931629.davem@davemloft.net> (raw)
In-Reply-To: <20120709203214.28178.71922.stgit@bhelgaas.mtv.corp.google.com>
From: Bjorn Helgaas <bhelgaas@google.com>
Date: Mon, 09 Jul 2012 14:32:14 -0600
> The generic code to read P2P bridge windows is functionally equivalent
> to the sparc-specific pci_cfg_fake_ranges(), so use the generic code.
>
> The "if (!res->start) res->start = ..." removed from the I/O window code
> here was an artifact of the Intel 1K window support from 9d265124d051 and
> is no longer necessary (it probably was just cloned from x86 and was never
> useful on sparc).
>
> CC: "David S. Miller" <davem@davemloft.net>
> CC: sparclinux@vger.kernel.org
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2012-07-09 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 20:31 [PATCH 0/3] PCI: P2P bridge window fixes Bjorn Helgaas
2012-07-09 20:32 ` [PATCH 1/3] PCI: allow P2P bridge windows starting at PCI bus address zero Bjorn Helgaas
2012-07-09 21:11 ` Yinghai Lu
2012-07-09 20:32 ` [PATCH 2/3] PCI: reimplement P2P bridge 1K I/O windows (Intel P64H2) Bjorn Helgaas
2012-07-09 21:43 ` Yinghai Lu
2012-07-09 22:21 ` Bjorn Helgaas
2012-07-09 23:50 ` Yinghai Lu
2012-07-09 20:32 ` [PATCH 3/3] sparc/PCI: replace pci_cfg_fake_ranges() with pci_read_bridge_bases() Bjorn Helgaas
2012-07-09 21:25 ` David Miller [this message]
2012-07-10 3:24 ` [PATCH 0/3] PCI: P2P bridge window fixes Bjorn Helgaas
2012-07-10 15:08 ` Bjorn Helgaas
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=20120709.142531.1530660875837931629.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhelgaas@google.com \
--cc=dan.yeisley@unisys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=yinghai@kernel.org \
/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).