From: Bjorn Helgaas <helgaas@kernel.org>
To: Roy Zang <roy.zang@nxp.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Minghuan Lian <minghuan.Lian@freescale.com>,
Mingkai Hu <mingkai.hu@freescale.com>,
Roy Zang <tie-fei.zang@freescale.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/7] PCI: layerscape: Name private struct pointer "ls" consistently
Date: Fri, 7 Oct 2016 13:21:25 -0500 [thread overview]
Message-ID: <20161007182125.GB30438@localhost> (raw)
In-Reply-To: <HE1PR0402MB27481312F256EBB295800F878BC60@HE1PR0402MB2748.eurprd04.prod.outlook.com>
On Fri, Oct 07, 2016 at 05:05:05PM +0000, Roy Zang wrote:
> On 10/07/2016 11:42 AM, Bjorn Helgaas wrote:
> > Use a device-specific name, "ls", for struct ls_pcie pointers
> > to hint that this is device-specific information. No functional change
> > intended.
> how about ls_pcie instead of ls ?
Done, and re-pushed the branch, thanks!
prev parent reply other threads:[~2016-10-07 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 16:41 [PATCH 1/7] PCI: layerscape: Name private struct pointer "ls" consistently Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 2/7] PCI: layerscape: Pass device-specific struct to internal functions Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 3/7] PCI: layerscape: Remove redundant struct ls_pcie.dbi Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 4/7] PCI: layerscape: Reorder struct ls_pcie Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 5/7] PCI: layerscape: Add local struct device pointers Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 6/7] PCI: layerscape: Move struct pcie_port setup to probe function Bjorn Helgaas
2016-10-07 16:42 ` [PATCH 7/7] PCI: layerscape: Remove unused ls_add_pcie_port() platform_device arg Bjorn Helgaas
2016-10-07 17:05 ` [PATCH 1/7] PCI: layerscape: Name private struct pointer "ls" consistently Roy Zang
2016-10-07 18:21 ` 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=20161007182125.GB30438@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minghuan.Lian@freescale.com \
--cc=mingkai.hu@freescale.com \
--cc=roy.zang@nxp.com \
--cc=tie-fei.zang@freescale.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.