From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <apatel@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
saravanak@google.com, devicetree@vger.kernel.org,
anup@brainfault.org, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, palmer@dabbelt.com,
atishp@atishpatra.org, ajones@ventanamicro.com
Subject: Re: [PATCH v4] of: property: Add fw_devlink support for interrupt-map property
Date: Wed, 22 May 2024 23:32:23 +0000 [thread overview]
Message-ID: <171642074362.9409.8597055988913469203.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240509120820.1430587-1-apatel@ventanamicro.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Rob Herring (Arm) <robh@kernel.org>:
On Thu, 9 May 2024 17:38:20 +0530 you wrote:
> Some of the PCI host controllers (such as generic PCI host controller)
> use "interrupt-map" DT property to describe the mapping between PCI
> endpoints and PCI interrupt pins. This is the only case where the
> interrupts are not described in DT.
>
> Currently, there is no fw_devlink created based on "interrupt-map"
> DT property so interrupt controller is not guaranteed to be probed
> before the PCI host controller. This affects every platform where
> both PCI host controller and interrupt controllers are probed as
> regular platform devices.
>
> [...]
Here is the summary with links:
- [v4] of: property: Add fw_devlink support for interrupt-map property
https://git.kernel.org/riscv/c/d976c6f4b32c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-22 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 12:08 [PATCH v4] of: property: Add fw_devlink support for interrupt-map property Anup Patel
2024-05-13 14:57 ` Rob Herring (Arm)
2024-05-22 23:32 ` patchwork-bot+linux-riscv [this message]
2024-05-28 16:36 ` Marc Zyngier
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=171642074362.9409.8597055988913469203.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).