linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: "Romli, Khairul Anuar" <khairul.anuar.romli@altera.com>
Cc: Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
	Tom Rix <trix@redhat.com>, Dinh Nguyen <dinguyen@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Rao, Mahesh" <mahesh.rao@altera.com>,
	"Ng, Adrian Ho Yin" <adrian.ho.yin.ng@altera.com>,
	"Rabara, Niravkumar Laxmidas" <nirav.rabara@altera.com>,
	"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: fpga: stratix10: add support for Agilex5
Date: Wed, 19 Nov 2025 17:49:12 +0000	[thread overview]
Message-ID: <20251119-crushed-supreme-9d22b030f507@spud> (raw)
In-Reply-To: <07575ce3-eab7-46dd-baad-8a909124a962@altera.com>

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

On Wed, Nov 19, 2025 at 01:45:03AM +0000, Romli, Khairul Anuar wrote:

> I will go through other bindings with rg --multiline that you shared and 
> will send next version after all the test is done.

Unless you're planning on fixing the ones that should not have contains,
that comment was only for Krzysztof.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-19 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 23:34 [PATCH v5 0/2] Enable FPGA Manager support for Agilex5 Khairul Anuar Romli
2025-11-18 23:34 ` [PATCH v5 1/2] dt-bindings: fpga: stratix10: add " Khairul Anuar Romli
2025-11-19  1:20   ` Conor Dooley
2025-11-19  1:45     ` Romli, Khairul Anuar
2025-11-19 17:49       ` Conor Dooley [this message]
2025-11-18 23:34 ` [PATCH v5 2/2] arm64: dts: agilex5: add fpga-region and fpga-mgr nodes Khairul Anuar Romli

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=20251119-crushed-supreme-9d22b030f507@spud \
    --to=conor@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=khairul.anuar.romli@altera.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@altera.com \
    --cc=mdf@kernel.org \
    --cc=nirav.rabara@altera.com \
    --cc=robh@kernel.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.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).