mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@riscstar.com>
To: Andrea della Porta <andrea.porta@suse.com>
Cc: bhelgaas@google.com, lizhi.hou@amd.com, herve.codina@bootlin.com,
	daniel@riscstar.com, mohdayaa@qti.qualcomm.com,
	lbiancon@qti.qualcomm.com, mani@kernel.org, robh@kernel.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] PCI: of: update endpoint ranges dynamically
Date: Thu, 8 Oct 2026 10:55:34 -0500	[thread overview]
Message-ID: <223c5189-bfda-4c63-b09f-4ebd01bd144a@riscstar.com> (raw)
In-Reply-To: <ase6toUhGn0XD0v9@apocalypse>

On 10/8/26 10:45 AM, Andrea della Porta wrote:
> After a quick test, it seems that it's not working out of the
> box on my RPi5. Let me investigate a bit to see what's wrong.

THANK YOU FOR TESTING THIS!!!

My hope was that the recent change (to avoid doing any
updating of ranges property unless it was found to be
"empty") would avoid any trouble with the RPi5.

I'm eager to hear what more you find.  Please let me
know if I can be of any other help.

					-Alex

      reply	other threads:[~2026-10-08 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 22:24 Alex Elder
2026-09-24 22:24 ` [PATCH v3 1/3] PCI: of: make a flags argument optional Alex Elder
2026-09-24 22:24 ` [PATCH v3 2/3] PCI: of: introduce of_pci_build_prop_ranges() Alex Elder
2026-09-24 22:24 ` [PATCH v3 3/3] PCI: of: introduce of_pci_update_endpoint_node_ranges() Alex Elder
2026-10-02 16:24 ` [PATCH v3 0/3] PCI: of: update endpoint ranges dynamically Alex Elder
2026-10-08 15:45 ` Andrea della Porta
2026-10-08 15:55   ` Alex Elder [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=223c5189-bfda-4c63-b09f-4ebd01bd144a@riscstar.com \
    --to=elder@riscstar.com \
    --cc=andrea.porta@suse.com \
    --cc=bhelgaas@google.com \
    --cc=daniel@riscstar.com \
    --cc=herve.codina@bootlin.com \
    --cc=lbiancon@qti.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=mani@kernel.org \
    --cc=mohdayaa@qti.qualcomm.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

all inboxes | Powered by JetHome®