From: Herve Codina <herve.codina@bootlin.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: interrupt-controller: microchip,lan966x-oic: Clarify endpoint use
Date: Mon, 20 Jan 2025 08:58:39 +0100 [thread overview]
Message-ID: <20250120085839.3982743c@bootlin.com> (raw)
In-Reply-To: <0f2d1bcb431827b65b2c0ba6619d9126ec97da72.1737118595.git.geert+renesas@glider.be>
Hi Geert,
On Fri, 17 Jan 2025 14:04:36 +0100
Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> Reword the description, to make it clear that the LAN966x Outbound
> Interrupt Controller is used only in PCI endpoint mode.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v2:
> - New.
> ---
> .../bindings/interrupt-controller/microchip,lan966x-oic.yaml | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
Acked-by: Herve Codina <herve.codina@bootlin.com>
Best regards,
Hervé
next prev parent reply other threads:[~2025-01-20 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 13:04 [PATCH v2 0/3] LAN966x PCIe endpoint cleanups Geert Uytterhoeven
2025-01-17 13:04 ` [PATCH v2 1/3] dt-bindings: interrupt-controller: microchip,lan966x-oic: Clarify endpoint use Geert Uytterhoeven
2025-01-18 14:23 ` Krzysztof Kozlowski
2025-01-20 7:58 ` Herve Codina [this message]
2025-01-17 13:04 ` [PATCH v2 2/3] irqchip: LAN966X_OIC should depend on MFD_LAN966X_PCI Geert Uytterhoeven
2025-01-20 7:59 ` Herve Codina
2025-01-20 10:52 ` Geert Uytterhoeven
2025-01-17 13:04 ` [PATCH v2 3/3] phy: PHY_LAN966X_SERDES should depend on SOC_LAN966 || MCHP_LAN966X_PCI Geert Uytterhoeven
2025-01-20 8:07 ` Herve Codina
2025-01-20 8:21 ` 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=20250120085839.3982743c@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=vkoul@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).