public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: intel: set alias for i3c controllers for agilex5 variants
Date: Mon, 4 May 2026 22:39:27 -0500	[thread overview]
Message-ID: <8822fe26-aacc-4167-b53c-9dabd23420d6@kernel.org> (raw)
In-Reply-To: <3f6a9abfac3ed7bdc37e891f6740e5bb6db47c11.1777951738.git.adrian.ho.yin.ng@altera.com>

Sorry if I was unclear, the commit header should be:

arm64: dts: socfpga: agilex5: set alias for i3c controllers

For future reference, please run a 'git log' on the files you're 
changing as an example.

On 5/4/26 22:30, Adrian Ng Ho Yin wrote:
> From: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>
> 
> Agilex5 SoCFPGA variants and derivities have 2 i3c controllers, a main
> master and a secondary master. Setting the alias for both i3c controllers
> to prevent bus id contention when both controllers are enabled which
> results in driver probe failures.
> 

Dinh

  reply	other threads:[~2026-05-05  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  3:30 [PATCH v2 0/2] arm64: dts: intel: set alias for i3c controllers for agilex5 variants and derivatives Adrian Ng Ho Yin
2026-05-05  3:30 ` [PATCH v2 1/2] arm64: dts: intel: set alias for i3c controllers for agilex5 variants Adrian Ng Ho Yin
2026-05-05  3:39   ` Dinh Nguyen [this message]
2026-05-05  3:30 ` [PATCH v2 2/2] arm64: dts: intel: set alias for i3c controllers for agilex3 Adrian Ng Ho Yin
2026-05-05  3:40   ` Dinh Nguyen

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=8822fe26-aacc-4167-b53c-9dabd23420d6@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=adrianhoyin.ng@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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