linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Phil Edworthy <phil.edworthy@renesas.com>,
	Simon Horman <horms+renesas@verge.net.au>,
	Wolfram Sang <wsa@the-dreams.de>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges()
Date: Wed, 23 May 2018 19:05:06 +0200	[thread overview]
Message-ID: <5fc7b4ff-1c75-4d3f-6cb7-fda4559a3635@gmail.com> (raw)
In-Reply-To: <20180523161711.GA8113@e107981-ln.cambridge.arm.com>

On 05/23/2018 06:17 PM, Lorenzo Pieralisi wrote:
> On Mon, May 21, 2018 at 03:11:20PM +0200, Marek Vasut wrote:
>> The function name is just too confusing, rename it, no functional change.
>> Rename the function to rcar_pcie_alloc_and_parse_pci_resource_list() as
>> it's matching failpath function is pci_free_resource_list() so the names
>> align much better and the new name also describes what the function does
>> much better.
>>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Phil Edworthy <phil.edworthy@renesas.com>
>> Cc: Simon Horman <horms+renesas@verge.net.au>
>> Cc: Wolfram Sang <wsa@the-dreams.de>
>> Cc: linux-renesas-soc@vger.kernel.org
>> ---
>>  drivers/pci/host/pcie-rcar.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Can you rebase this series against my pci/rcar branch please ?
> 
> I will merge it then, thanks.

Where is that tree/branch located ?

It applies fine on current next 20180517, is there a problem ?

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-05-23 17:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 13:11 [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Marek Vasut
2018-05-21 13:11 ` [PATCH 2/4] PCI: rcar: Pull bus clock enable/disable from rcar_pcie_get_resources() Marek Vasut
2018-05-22  9:13   ` Simon Horman
2018-05-22 15:11   ` Geert Uytterhoeven
2018-05-21 13:11 ` [PATCH 3/4] PCI: rcar: Add missing irq_dispose_mapping() into failpath Marek Vasut
2018-05-22  9:14   ` Simon Horman
2018-05-22 15:18   ` Geert Uytterhoeven
2018-05-22 21:51     ` Marek Vasut
2018-05-21 13:11 ` [PATCH 4/4] PCI: rcar: Teardown MSI setup if rcar_pcie_enable() fails Marek Vasut
2018-05-22  9:16   ` Simon Horman
2018-05-22 18:36   ` Geert Uytterhoeven
2018-05-22 21:53     ` Marek Vasut
2018-05-23  6:18       ` Geert Uytterhoeven
2018-05-23 10:38         ` Marek Vasut
2018-05-22  9:12 ` [PATCH 1/4] PCI: rcar: Rename rcar_pcie_parse_request_of_pci_ranges() Simon Horman
2018-05-22 10:53 ` Geert Uytterhoeven
2018-05-23 16:17 ` Lorenzo Pieralisi
2018-05-23 17:05   ` Marek Vasut [this message]
2018-05-23 21:56     ` Bjorn Helgaas
2018-05-24  7:24       ` Marek Vasut
2018-05-24 13:50         ` Lorenzo Pieralisi
2018-05-24 14:36           ` Marek Vasut

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=5fc7b4ff-1c75-4d3f-6cb7-fda4559a3635@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=phil.edworthy@renesas.com \
    --cc=wsa@the-dreams.de \
    /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).