From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [GIT PULL] PCI: tegra: Changes for v4.8-rc1
Date: Fri, 1 Jul 2016 17:00:56 +0200 [thread overview]
Message-ID: <20160701150056.26537-3-thierry.reding@gmail.com> (raw)
Hi Bjorn,
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.8-pci
for you to fetch changes up to 0f32700faed919946e21e9d1dc4d74ae8f1b1226:
PCI: tegra: Correctly program PADS_REFCLK_CFG* registers (2016-06-30 15:30:16 +0200)
There's a minor conflict between this and your pci/host-request-windows
branch, let me know if you'd like me to rebase on top of that.
Thierry
----------------------------------------------------------------
PCI: tegra: Changes for v4.8-rc1
A couple of cleanups and preparation work for 64-bit ARM support, as
well as fixes for writing the PADS_REFCLK_CFG* registers.
----------------------------------------------------------------
Stephen Warren (2):
PCI: tegra: Actually program PADS_REFCLK_CFG* on recent SoCs
PCI: tegra: Correctly program PADS_REFCLK_CFG* registers
Thierry Reding (3):
PCI: tegra: Make register definitions consistent
PCI: tegra: Use pci_remap_iospace()
PCI: tegra: Stop setting pcibios_min_mem
drivers/pci/host/pci-tegra.c | 54 ++++++++++++++++++++------------------------
1 file changed, 25 insertions(+), 29 deletions(-)
next reply other threads:[~2016-07-01 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 15:00 Thierry Reding [this message]
2016-07-26 20:06 ` [GIT PULL] PCI: tegra: Changes for v4.8-rc1 Bjorn Helgaas
2016-07-28 14:18 ` Thierry Reding
2016-07-28 15:59 ` Stephen Warren
[not found] ` <20160701150056.26537-3-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-26 20: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=20160701150056.26537-3-thierry.reding@gmail.com \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).