Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manikandan Karunakaran Pillai <mpillai@cadence.com>,
	"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"kw@linux.com" <kw@linux.com>,
	"robh@kernel.org" <robh@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Milind Parab <mparab@cadence.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/6] dt-bindings: pci: cadence: Add property "hpa" for PCIe controllers
Date: Tue, 25 Mar 2025 07:57:33 +0100	[thread overview]
Message-ID: <53eb9d35-2b7c-4742-af18-e7b0fb1cdcfe@kernel.org> (raw)
In-Reply-To: <DS0PR07MB10492F672DEACE769F97C609BA2A72@DS0PR07MB10492.namprd07.prod.outlook.com>

On 25/03/2025 04:16, Manikandan Karunakaran Pillai wrote:
> 
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Monday, March 24, 2025 9:29 PM
>> To: Manikandan Karunakaran Pillai <mpillai@cadence.com>;
>> lpieralisi@kernel.org; manivannan.sadhasivam@linaro.org;
>> bhelgaas@google.com; kw@linux.com; robh@kernel.org;
>> devicetree@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org; linux-pci@vger.kernel.org
>> Subject: Re: [PATCH 1/6] dt-bindings: pci: cadence: Add property "hpa" for PCIe
>> controllers
>>
>> EXTERNAL MAIL
>>
>>
>> On 24/03/2025 10:08, Manikandan Karunakaran Pillai wrote:
>>> Document the newly added property "hpa" for Cadence PCIe controllers
>>> in Documentation/devicetree/bindings/pci/ for Root Port and Endpoint
>>> configurations
>>
>> Drop the path, pointless.
> Ok
>>
>>>
>>
>> Please run scripts/checkpatch.pl on the patches and fix reported warnings.
>> After that, run also 'scripts/checkpatch.pl --strict' on the patches and
>> (probably) fix more warnings. Some warnings can be ignored, especially from -
>> -strict run, but the code here looks like it needs a fix. Feel free to get in touch if
>> the warning is not clear.
>>
> 
> The scripts/checkpatch.pl has been run  with and without --strict. With the --strict option
> 4 checks are generated on 1 patch(patch 0002 of the series), which can be ignored. There are 
> no code fixes required for these checks. The rest of the 'scripts/checkpatch.pl' 
> is clean.

No, it's not. The patch has obvious style violations.


> 
>> <form letter>
>> Please use scripts/get_maintainers.pl to get a list of necessary people and lists
>> to CC (and consider --no-git-fallback argument, so you will not CC people just
>> because they made one commit years ago). It might happen, that command
>> when run on an older kernel, gives you outdated entries. Therefore please be
>> sure you base your patches on recent Linux kernel.
> 
> Ok
> 
>>
>> Tools like b4 or scripts/get_maintainer.pl provide you proper list of people, so
>> fix your workflow. Tools might also fail if you work on some ancient tree (don't,
>> instead use mainline) or work on fork of kernel (don't, instead use mainline).
>> Just use b4 and everything should be fine, although remember about `b4 prep
>> --auto-to-cc` if you added new patches to the patchset.
>> </form letter>
>>
> I used an earlier list generated. Will take care to generate the list on latest tree.

That's not the correct process. Why would you Cc maintainers from 10
years ago?


Best regards,
Krzysztof

      reply	other threads:[~2025-03-25  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250324082335.2566055-1-mpillai@cadence.com>
2025-03-24  9:08 ` [PATCH 1/6] dt-bindings: pci: cadence: Add property "hpa" for PCIe controllers Manikandan Karunakaran Pillai
2025-03-24 15:59   ` Krzysztof Kozlowski
2025-03-25  3:16     ` Manikandan Karunakaran Pillai
2025-03-25  6:57       ` 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=53eb9d35-2b7c-4742-af18-e7b0fb1cdcfe@kernel.org \
    --to=krzk@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mparab@cadence.com \
    --cc=mpillai@cadence.com \
    --cc=robh@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