linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: hans.zhang@cixtech.com, bhelgaas@google.com,
	lpieralisi@kernel.org, kw@linux.com,
	manivannan.sadhasivam@linaro.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: peter.chen@cixtech.com, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Enhance the PCIe controller driver
Date: Fri, 25 Apr 2025 18:24:32 +0200	[thread overview]
Message-ID: <df9da79c-dc1a-4e90-82eb-f3af71f13494@kernel.org> (raw)
In-Reply-To: <20250424010445.2260090-1-hans.zhang@cixtech.com>

On 24/04/2025 03:04, hans.zhang@cixtech.com wrote:
> From: Hans Zhang <hans.zhang@cixtech.com>
> 
> Enhances the exiting Cadence PCIe controller drivers to support
> HPA (High Performance Architecture) Cadence PCIe controllers.
> 
> The patch set enhances the Cadence PCIe driver for HPA support.
> The "compatible" property in DTS is added with  more enum to support
> the new platform architecture and the register maps that change with
> it. The driver read register and write register functions take the
> updated offset stored from the platform driver to access the registers.
> The driver now supports the legacy and HPA architecture, with the
> legacy code changes beingminimal.
> 
> SoC related changes are not available in this patch set.
> 
> The TI SoC continues to be supported with the changes incorporated.
> 
> The changes are also in tune with how multiple platforms are supported
> in related drivers.
> 
> The scripts/checkpatch.pl has been run on the patches with and without
> --strict. With the --strict option, 4 checks are generated on 1 patch
> (PATCH v3 3/6) 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.
> 
> The ./scripts/kernel-doc --none have been run on the changed files.
> 
> The changes are tested on TI platforms. The legacy controller changes are
> tested on an TI J7200 EVM and HPA changes are planned for on an FPGA
> platform available within Cadence.
> 
> Changes for v4
> 	- Add header file bitfield.h to pcie-cadence.h.
> 	- Addressed the following review comments.
> 	  Merged the TI patch as it.
> 	  Removed initialization of struct variables to '0'.

So the rest you did not address?

That's not acceptable. You ignored several comments such way. Either
discussion did not finish or you agree to implement all comments. If you
do not agree, then sending new version hides the previous discussion.
Best regards,
Krzysztof

      parent reply	other threads:[~2025-04-25 16:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  1:04 [PATCH v4 0/5] Enhance the PCIe controller driver hans.zhang
2025-04-24  1:04 ` [PATCH v4 1/5] dt-bindings: pci: cadence: Extend compatible for new RP configuration hans.zhang
2025-04-24  1:04 ` [PATCH v4 2/5] dt-bindings: pci: cadence: Extend compatible for new EP configurations hans.zhang
2025-04-24 15:29   ` Conor Dooley
2025-04-24 15:30     ` Conor Dooley
2025-04-25  2:19       ` Manikandan Karunakaran Pillai
2025-04-25 14:48         ` Conor Dooley
2025-04-25 15:33           ` Hans Zhang
2025-04-25 16:21             ` Krzysztof Kozlowski
2025-04-25 16:47               ` Hans Zhang
2025-04-27  3:55               ` Manikandan Karunakaran Pillai
2025-04-27 19:08                 ` Krzysztof Kozlowski
2025-04-25  2:17     ` Manikandan Karunakaran Pillai
2025-04-24  1:04 ` [PATCH v4 3/5] PCI: cadence: Add header support for PCIe HPA controller hans.zhang
2025-04-24  3:36   ` Peter Chen (CIX)
2025-04-25  4:18   ` kernel test robot
2025-04-24  1:04 ` [PATCH v4 4/5] PCI: cadence: Add support for PCIe Endpoint " hans.zhang
2025-04-24  1:04 ` [PATCH v4 5/5] PCI: cadence: Add callback functions for RP and EP controller hans.zhang
2025-04-25  6:01   ` kernel test robot
2025-04-25 16:27   ` Krzysztof Kozlowski
2025-04-25 16:51     ` Hans Zhang
2025-04-27  3:52     ` Manikandan Karunakaran Pillai
2025-06-01 14:40       ` manivannan.sadhasivam
2025-06-02  1:24         ` Manikandan Karunakaran Pillai
2025-04-25 16:24 ` 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=df9da79c-dc1a-4e90-82eb-f3af71f13494@kernel.org \
    --to=krzk@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hans.zhang@cixtech.com \
    --cc=krzk+dt@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=peter.chen@cixtech.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;
as well as URLs for NNTP newsgroup(s).