From: Bjorn Helgaas <helgaas@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCI: tegra: Cleanups
Date: Wed, 12 Oct 2016 11:02:17 -0500 [thread overview]
Message-ID: <20161012160217.GF4308@localhost> (raw)
In-Reply-To: <20161012125946.24960.54201.stgit@bhelgaas-glaptop2.roam.corp.google.com>
On Wed, Oct 12, 2016 at 08:02:12AM -0500, Bjorn Helgaas wrote:
> - Fix argument order bug for pads_writel() call.
>
> - Add local "dev" pointers to reduce repetition of things like
> "&pdev->dev".
>
> - Remove platform drvdata because it appears unused (we called
> platform_set_drvdata() but not platform_get_drvdata()).
>
> The first patch fixes a bug. The others shouldn't change the behavior.
>
> Changes from v1:
> I dropped the following patches because they were a lot of churn for
> questionable benefit:
> PCI: tegra: Swap order of afi_writel() reg/val arguments
> PCI: tegra: Swap order of pads_writel() reg/val arguments
>
> ---
>
> Bjorn Helgaas (3):
> PCI: tegra: Fix argument order in tegra_pcie_phy_disable()
> PCI: tegra: Add local struct device pointers
> PCI: tegra: Remove unused platform data
I applied these to pci/host-tegra for v4.9. I hope to ask Linus to
pull them tomorrow, so if you see any issues, let me know soon.
prev parent reply other threads:[~2016-10-12 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:02 [PATCH v2 0/3] PCI: tegra: Cleanups Bjorn Helgaas
2016-10-12 13:02 ` [PATCH v2 1/3] PCI: tegra: Fix argument order in tegra_pcie_phy_disable() Bjorn Helgaas
2016-10-12 13:02 ` [PATCH v2 2/3] PCI: tegra: Add local struct device pointers Bjorn Helgaas
2016-10-12 13:02 ` [PATCH v2 3/3] PCI: tegra: Remove unused platform data Bjorn Helgaas
2016-10-12 13:02 ` Bjorn Helgaas
2016-10-12 16:02 ` Bjorn Helgaas [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=20161012160217.GF4308@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gnurou@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.