public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans Zhang <18255117159@163.com>
Cc: "Gerd Bayer" <gbayer@linux.ibm.com>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Hans Zhang" <hans.zhang@cixtech.com>,
	"Arnd Bergmann" <arnd@kernel.org>,
	bhelgaas@google.com, "Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	jingoohan1@gmail.com,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-next <linux-next@vger.kernel.org>,
	linux-pci@vger.kernel.org,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Niklas Schnelle" <schnelle@linux.ibm.com>,
	geert@linux-m68k.org
Subject: Re: [PATCH] PCI: Fix endianness issues in pci_bus_read_config()
Date: Mon, 4 Aug 2025 09:33:13 -0500	[thread overview]
Message-ID: <20250804143313.GA3624395@bhelgaas> (raw)
In-Reply-To: <06012cc6-824d-4a7d-85c9-9995ec915382@163.com>

On Mon, Aug 04, 2025 at 11:06:36AM +0800, Hans Zhang wrote:
> ...

> According to the issue mentioned by Lukas and Mani. Gerd has already been
> tested on the s390. I have tested it on the RK3588 and it works fine. RK3588
> uses Synopsys' PCIe IP, that is, the DWC driver. Our company's is based on
> Cadence's PCIe 4.0 IP, and the test function is normal. All the platforms I
> tested were based on ARM.
> 
> The following is the patch based on the capability-search branch. May I ask
> everyone, do you have any more questions?
> 
> Gerd, if there's no problem, I'll add your Tested-by label.
> 
> Branch: ttps://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/log/?h=capability-search

Since this series will now target v6.18, I'll watch for a complete v15
series based on v6.17-rc1, with this fix and any typo or other fixes
from pci/capability-search fully integrated.

Then that series can be tested and completely replace the current
pci/capability-search branch.

Bjorn

  parent reply	other threads:[~2025-08-04 14:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250716231121.GA2564572@bhelgaas>
2025-07-31  7:32 ` [REGRESSION] next/master: suspect endianness issue in common PCI capability search macro Gerd Bayer
2025-07-31 17:38   ` [PATCH] PCI: Fix endianness issues in pci_bus_read_config() Gerd Bayer
2025-07-31 18:39     ` Bjorn Helgaas
2025-07-31 19:01       ` Arnd Bergmann
2025-08-01  8:18         ` Manivannan Sadhasivam
2025-08-01  9:25           ` Hans Zhang
2025-08-01  9:47             ` Manivannan Sadhasivam
2025-08-01 10:06               ` Hans Zhang
2025-08-01 10:54                 ` Manivannan Sadhasivam
2025-08-01 11:30                   ` Gerd Bayer
2025-08-01 16:54                     ` Hans Zhang
2025-08-01 18:08                       ` Keith Busch
2025-08-02 15:23                         ` Hans Zhang
2025-08-02 15:40                           ` Arnd Bergmann
2025-08-04  3:06                     ` Hans Zhang
2025-08-04  8:03                       ` Arnd Bergmann
2025-08-04  8:25                         ` Hans Zhang
2025-08-04 10:09                       ` Gerd Bayer
2025-08-12 14:44                         ` Hans Zhang
2025-08-13  7:47                           ` Niklas Schnelle
2025-08-13  7:50                             ` Hans Zhang
2025-08-04 14:33                       ` Bjorn Helgaas [this message]
2025-08-04 15:04                         ` Hans Zhang
2025-08-01 16:47                   ` Hans Zhang
2025-07-31 18:53     ` Lukas Wunner
2025-08-01  7:52     ` Geert Uytterhoeven

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=20250804143313.GA3624395@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=18255117159@163.com \
    --cc=agordeev@linux.ibm.com \
    --cc=arnd@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gbayer@linux.ibm.com \
    --cc=geert@linux-m68k.org \
    --cc=hans.zhang@cixtech.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jingoohan1@gmail.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@kernel.org \
    --cc=schnelle@linux.ibm.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