From: Bjorn Helgaas <bhelgaas@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: [GIT PULL] PCI fixes for v3.18
Date: Wed, 3 Dec 2014 11:30:36 -0700 [thread overview]
Message-ID: <20141203183036.GA19435@google.com> (raw)
Hi Linus,
This fixes a Tegra20 regression that we introduced during the v3.18 merge
window.
Bjorn
The following changes since commit 7fc986d8a9727e5d40da3c2c1c343da6142e82a9:
PCI: Support 64-bit bridge windows if we have 64-bit dma_addr_t (2014-11-19 14:30:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v3.18-fixes-4
for you to fetch changes up to 5106787a9e08dc2901d6b2513ed8f377671befa8:
PCI: tegra: Use physical range for I/O mapping (2014-12-01 16:55:43 -0700)
----------------------------------------------------------------
PCI update for v3.18:
NVIDIA Tegra
- Use physical range for I/O mapping (Thierry Reding)
----------------------------------------------------------------
Thierry Reding (1):
PCI: tegra: Use physical range for I/O mapping
drivers/pci/host/pci-tegra.c | 28 ++++++++++++++++++++--------
1 file changed, 20 insertions(+), 8 deletions(-)
next reply other threads:[~2014-12-03 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 18:30 Bjorn Helgaas [this message]
[not found] <20141120194422.GA6923@google.com>
2014-11-20 21:10 ` [GIT PULL] PCI fixes for v3.18 Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2014-11-06 18:54 Bjorn Helgaas
2014-10-31 16:54 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=20141203183036.GA19435@google.com \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=treding@nvidia.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).