SUPERH platform development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Simon Horman <horms@verge.net.au>,
	linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/2] PCI: host: pcie-rcar: Style and formatting changes.
Date: Sat, 28 Jun 2014 00:22:19 +0000	[thread overview]
Message-ID: <53AE0ABB.4010501@cogentembedded.com> (raw)
In-Reply-To: <20140628001542.GA32431@verge.net.au>

Hello.

On 06/28/2014 04:15 AM, Simon Horman wrote:

>>> This patch just makes symbol and function name changes to avoid
>>> potential conflicts, along with minor formatting changes.
>>> The only other change is to replace an arg passed into a func
>>> with a local variable.

>>> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
>>> ---
>>>   drivers/pci/host/pcie-rcar.c | 131 ++++++++++++++++++++++---------------------
>>>   1 file changed, 67 insertions(+), 64 deletions(-)

>>> diff --git a/drivers/pci/host/pcie-rcar.c b/drivers/pci/host/pcie-rcar.c
>>> index 680a8cc..efdea07 100644
>>> --- a/drivers/pci/host/pcie-rcar.c
>>> +++ b/drivers/pci/host/pcie-rcar.c
[...]
>>> @@ -318,14 +319,15 @@ static struct pci_ops rcar_pcie_ops = {
>>>   	.write	= rcar_pcie_write_conf,
>>>   };
>>>
>>> -static void rcar_pcie_setup_window(int win, struct resource *res,
>>> -				   struct rcar_pcie *pcie)
>>> +static void rcar_pcie_setup_window(int win, struct rcar_pcie *pcie)
>>>   {
>>> +	struct resource *res = &pcie->res[win];
>>> +
>>
>> The removal of the res parameter is not in keeping with the changelog.
>> Could you break it out into a separate patch?
>
> Sorry, I see that it is mentioned in the changelog.
> But could you split the patch all the same?

    I agree. Generally, you should not mix several changes of a different 
nature in one patch.

WBR, Sergei


      reply	other threads:[~2014-06-28  0:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 16:55 [PATCH 0/2] PCI: host: pcie-rcar: minor clean ups Phil Edworthy
2014-06-27 16:55 ` [PATCH 1/2] PCI: host: pcie-rcar: Use correct initial HW settings Phil Edworthy
2014-06-27 16:55 ` [PATCH 2/2] PCI: host: pcie-rcar: Style and formatting changes Phil Edworthy
2014-06-28  0:14   ` Simon Horman
2014-06-28  0:15     ` Simon Horman
2014-06-28  0:22       ` Sergei Shtylyov [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=53AE0ABB.4010501@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=bhelgaas@google.com \
    --cc=horms@verge.net.au \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=phil.edworthy@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox