public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Potin Lai <potin.lai.pt@gmail.com>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Patrick Williams <patrick@stwcx.xyz>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Cosmo Chou <cosmo.chou@quantatw.com>,
	Mike Hsieh <Mike_Hsieh@quantatw.com>,
	Potin Lai <potin.lai@quantatw.com>,
	Roger Kan <Roger.Kan@quantatw.com>
Subject: Re: [PATCH v2 2/2] ARM: dts: aspeed: add Meta SanMiguel BMC
Date: Mon, 09 Feb 2026 17:22:47 +1030	[thread overview]
Message-ID: <e7671063304f1bfdb66bc4e7d271c9e836bbe3cc.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20260203-sanmiguel_init_dts-v2-2-6a5682c32b38@gmail.com>

On Tue, 2026-02-03 at 17:48 +0800, Potin Lai wrote:
> Add linux device tree entry for Meta (Facebook) SanMiguel compute-
> tray
> BMC using AT2620 SoC.
> 
> Signed-off-by: Potin Lai <potin.lai.pt@gmail.com>

Ah, I missed that there was a v2, however my comments on the v1 DTS
still appear to apply. Can you address them?

Andrew

  reply	other threads:[~2026-02-09  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03  9:48 [PATCH v2 0/2] Add Meta (Facebook) SanMiguel BMC (AST2620) Potin Lai
2026-02-03  9:48 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add Meta SanMiguel BMC Potin Lai
2026-02-04 18:04   ` Conor Dooley
2026-02-03  9:48 ` [PATCH v2 2/2] ARM: dts: " Potin Lai
2026-02-09  6:52   ` Andrew Jeffery [this message]
2026-02-03 13:42 ` [PATCH v2 0/2] Add Meta (Facebook) SanMiguel BMC (AST2620) Andrew Lunn
2026-03-11  6:31   ` Potin Lai
2026-03-11 12:36     ` Andrew Lunn

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=e7671063304f1bfdb66bc4e7d271c9e836bbe3cc.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=Mike_Hsieh@quantatw.com \
    --cc=Roger.Kan@quantatw.com \
    --cc=conor+dt@kernel.org \
    --cc=cosmo.chou@quantatw.com \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick@stwcx.xyz \
    --cc=potin.lai.pt@gmail.com \
    --cc=potin.lai@quantatw.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