linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 01/10] PCI: rcar: Rename accessors
Date: Sat, 8 Oct 2016 11:37:52 +0900	[thread overview]
Message-ID: <20161008023752.GC14617@verge.net.au> (raw)
In-Reply-To: <20161007162446.23279.48813.stgit@bhelgaas-glaptop2.roam.corp.google.com>

On Fri, Oct 07, 2016 at 11:24:46AM -0500, Bjorn Helgaas wrote:
> Rename rcar_pci_read_reg() to rcar_readl() and rcar_pci_write_reg() to
> rcar_writel() for consistency with other drivers.  No functional change
> intended.
> 
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

I am fine with this entire series.

Acked-by: Simon Horman <horms+renesas@verge.net.au>

> ---
>  drivers/pci/host/pcie-rcar.c |  142 ++++++++++++++++++++----------------------
>  1 file changed, 68 insertions(+), 74 deletions(-)
> 
> diff --git a/drivers/pci/host/pcie-rcar.c b/drivers/pci/host/pcie-rcar.c
> index e06b1d3..b6899c8 100644
> --- a/drivers/pci/host/pcie-rcar.c
> +++ b/drivers/pci/host/pcie-rcar.c
> @@ -152,16 +152,15 @@ struct rcar_pcie {
>  	struct			rcar_msi msi;
>  };
>  
> -static void rcar_pci_write_reg(struct rcar_pcie *pcie, unsigned long val,
> -			       unsigned long reg)
> +static unsigned long rcar_readl(struct rcar_pcie *pcie, unsigned long reg)
>  {
> -	writel(val, pcie->base + reg);
> +	return readl(pcie->base + reg);
>  }
>  
> -static unsigned long rcar_pci_read_reg(struct rcar_pcie *pcie,
> -				       unsigned long reg)
> +static void rcar_writel(struct rcar_pcie *pcie, unsigned long val,
> +			unsigned long reg)
>  {
> -	return readl(pcie->base + reg);
> +	writel(val, pcie->base + reg);
>  }

The diff might have been a bit easier on the eyes if rcar_pci_write_reg()
was after rcar_pci_read_reg()

      parent reply	other threads:[~2016-10-08 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 16:24 [PATCH 01/10] PCI: rcar: Rename accessors Bjorn Helgaas
2016-10-07 16:24 ` [PATCH 02/10] PCI: rcar: Name private struct pointer "rcar" consistently Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 03/10] PCI: rcar: Swap order of rcar_writel() reg/val arguments Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 04/10] PCI: rcar: Add local struct device pointers Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 05/10] PCI: rcar: Remove unused rcar_pcie_get_resources() platform_device arg Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 06/10] PCI: rcar: Remove unused platform data Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 07/10] PCI: rcar: Remove DRV_NAME macro Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 08/10] PCI: rcar-gen2: Name private struct pointer "rcar" consistently Bjorn Helgaas
2016-10-07 16:25 ` [PATCH 09/10] PCI: rcar-gen2: Add register accessors Bjorn Helgaas
2016-10-07 16:26 ` [PATCH 10/10] PCI: rcar-gen2: Add local struct device pointers Bjorn Helgaas
2016-10-08  2:37 ` Simon Horman [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=20161008023752.GC14617@verge.net.au \
    --to=horms@verge.net.au \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.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).