linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	linux-pci@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/8] PCI: exynos: Name private struct pointer "exynos" consistently
Date: Mon, 10 Oct 2016 19:49:42 +0300	[thread overview]
Message-ID: <20161010164942.GA3352@kozik-lap> (raw)
In-Reply-To: <20161010133644.GA30267@localhost>

On Mon, Oct 10, 2016 at 08:36:44AM -0500, Bjorn Helgaas wrote:
> Hi Krzysztof,
> 
> Thanks a lot for taking the time to look these over.
> 
> On Sat, Oct 08, 2016 at 10:41:44PM +0300, Krzysztof Kozlowski wrote:
> > On Fri, Oct 07, 2016 at 11:35:26AM -0500, Bjorn Helgaas wrote:
> > > Use a device-specific name, "exynos", for struct exynos_pcie pointers
> > > to hint that this is device-specific information.
> > 
> > I don't get it. "exynos_pcie" is already a exynos-device-specific name.
> > There are a lot of changes but I don't see the real reason/benefit. What
> > was your intention?
> 
> I'm looking across all the drivers in drivers/pci/host/, not just
> exynos.  Many of them used "pcie" as name for pointers to the
> device-specific struct, leading to things like "pcie->lut" or
> "pcie->breg_base".  These *look* like they should be sort of generic,
> but in fact they are device-specific.
> 
> My idea was to replace that "pcie" name with something
> device-specific, and I started with the simplest possible name, e.g.,
> "exynos".  Others pointed out that that for SoCs, that is often not
> enough specific enough, and something like "exynos_pcie" is more
> appropriate.
> 
> In the specific case of exynos, it already uses "exynos_pcie" in most
> cases, so I tweaked this patch to use it in the few remaining places
> where it didn't (the register accessor functions).

Thanks for clarification, I am fine with it.

> > > No functional change
> > > intended.
> > 
> > Oh, but there is. Inline disappeared in first functions. Although I
> > don't mind but this should be seprate from trivial rename.
> 
> I didn't think of "inline" as a functional change, but I split it out
> into its own patch.  I'm embarrassed at how much churn this turned out
> to be, so I didn't want to add more patches than I had to, but I did
> split it out for you.
> 
> I repushed the branch.

Thanks,
Krzysztof

      reply	other threads:[~2016-10-10 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 16:35 [PATCH 1/8] PCI: exynos: Name private struct pointer "exynos" consistently Bjorn Helgaas
2016-10-07 16:35 ` [PATCH 2/8] PCI: exynos: Pass device-specific struct to internal functions Bjorn Helgaas
2016-10-07 16:35 ` [PATCH 3/8] PCI: exynos: Reorder struct exynos_pcie Bjorn Helgaas
2016-10-07 16:35 ` [PATCH 4/8] PCI: exynos: Reorder accessor functions Bjorn Helgaas
2016-10-07 16:36 ` [PATCH 5/8] PCI: exynos: Swap order of exynos_elb_writel() reg/val arguments Bjorn Helgaas
2016-10-07 16:36 ` [PATCH 6/8] PCI: exynos: Swap order of exynos_phy_writel() " Bjorn Helgaas
2016-10-07 16:36 ` [PATCH 7/8] PCI: exynos: Swap order of exynos_blk_writel() " Bjorn Helgaas
2016-10-07 16:36 ` [PATCH 8/8] PCI: exynos: Add local struct device pointers Bjorn Helgaas
2016-10-08 19:41 ` [PATCH 1/8] PCI: exynos: Name private struct pointer "exynos" consistently Krzysztof Kozlowski
2016-10-10 13:36   ` Bjorn Helgaas
2016-10-10 16:49     ` Krzysztof Kozlowski [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=20161010164942.GA3352@kozik-lap \
    --to=krzk@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-samsung-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).