From: Bjorn Helgaas <helgaas@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Zhou Wang <wangzhou1@hisilicon.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/8] PCI: hisi: Cleanups
Date: Wed, 12 Oct 2016 11:05:49 -0500 [thread overview]
Message-ID: <20161012160548.GO4308@localhost> (raw)
In-Reply-To: <20161012133904.28562.74066.stgit@bhelgaas-glaptop2.roam.corp.google.com>
On Wed, Oct 12, 2016 at 08:42:27AM -0500, Bjorn Helgaas wrote:
> - 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()).
>
> - Name private struct pointer consistently within driver.
>
> - Remove redundant struct members.
>
> - Use generic DesignWare accessors when possible.
>
> - Pass device-specific struct to internal functions for consistency.
>
> - Include register block base in PCIE_SYS_STATE4 address to simplify
> users.
>
> Nothing here should change the behavior of the driver.
>
> Changes from v1:
> I dropped the following patches because they were a lot of churn for
> questionable benefit:
> PCI: hisi: Rename APB accessors
> PCI: hisi: Rename config accessors
> PCI: hisi: Name private struct pointer "hisi" consistently
> (Instead of renaming *all* the pointers, I only renamed enough to
> make them consistent within this file.)
> PCI: hisi: Swap order of hisi_apb_writel() reg/val arguments
>
> ---
>
> Bjorn Helgaas (8):
> PCI: hisi: Add local struct device pointers
> PCI: hisi: Remove unused platform data
> PCI: hisi: Name private struct pointer "hisi_pcie" consistently
> PCI: hisi: Remove redundant struct hisi_pcie.reg_base
> PCI: hisi: Use generic DesignWare accessors
> PCI: hisi: Include register block base in PCIE_SYS_STATE4 address
> PCI: hisi: Pass device-specific struct to internal functions
> PCI: hisi: Reorder struct hisi_pcie
>
>
> drivers/pci/host/pcie-hisi.c | 86 +++++++++++++++++-------------------------
> 1 file changed, 35 insertions(+), 51 deletions(-)
I applied these to pci/host-hisi for v4.9. I hope to ask Linus to
pull them tomorrow, so if you see any issues, let me know soon.
next prev parent reply other threads:[~2016-10-12 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:42 [PATCH v2 0/8] PCI: hisi: Cleanups Bjorn Helgaas
2016-10-12 13:42 ` [PATCH v2 1/8] PCI: hisi: Add local struct device pointers Bjorn Helgaas
2016-10-12 13:42 ` [PATCH v2 2/8] PCI: hisi: Remove unused platform data Bjorn Helgaas
2016-10-12 13:42 ` [PATCH v2 3/8] PCI: hisi: Name private struct pointer "hisi_pcie" consistently Bjorn Helgaas
2016-10-12 13:42 ` [PATCH v2 4/8] PCI: hisi: Remove redundant struct hisi_pcie.reg_base Bjorn Helgaas
2016-10-12 13:43 ` [PATCH v2 5/8] PCI: hisi: Use generic DesignWare accessors Bjorn Helgaas
2016-10-12 13:43 ` [PATCH v2 6/8] PCI: hisi: Include register block base in PCIE_SYS_STATE4 address Bjorn Helgaas
2016-10-12 13:43 ` [PATCH v2 7/8] PCI: hisi: Pass device-specific struct to internal functions Bjorn Helgaas
2016-10-12 13:43 ` [PATCH v2 8/8] PCI: hisi: Reorder struct hisi_pcie Bjorn Helgaas
2016-10-12 16:05 ` Bjorn Helgaas [this message]
2016-10-14 2:19 ` [PATCH v2 0/8] PCI: hisi: Cleanups Gabriele Paoloni
2016-10-14 2:17 ` Gabriele Paoloni
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=20161012160548.GO4308@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=wangzhou1@hisilicon.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.