mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Neil Cheng <neilcheng0417@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, 	conor+dt@kernel.org,
	joel@jms.id.au, geert+renesas@glider.be, 	magnus.damm@gmail.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	 linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add Meta Rainiera6 BMC support
Date: Wed, 27 May 2026 11:36:46 +0930	[thread overview]
Message-ID: <e059b59ecb9b0912ae8a044e3f745450b7095573.camel@codeconstruct.com.au> (raw)
In-Reply-To: <cover.1779157117.git.neilcheng0417@gmail.com>

Hi Neil,

On Tue, 2026-05-19 at 10:38 +0800, Neil Cheng wrote:
> Add initial device tree support for the Meta Rainiera6 platform.
> 
> Changes in v2:
> 
> - reorder adc0/adc1 properties
> - add Acked-by from Conor Dooley
> 
> This series adds:
> - Meta Rainiera6 compatible entry
> - Rainiera6 BMC DTS

In the future can you please avoid threading v2 (and later) under your
prior submissions?

Thanks,

Andrew

  parent reply	other threads:[~2026-05-27  2:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  8:13 [PATCH " Neil Cheng
2026-05-18  8:13 ` [PATCH 1/2] dt-bindings: arm: aspeed: Add Meta Rainiera6 board Neil Cheng
2026-05-18 16:28   ` Conor Dooley
2026-05-18  8:13 ` [PATCH 2/2] ARM: dts: aspeed: rainiera6: Add Meta Rainiera6 BMC Neil Cheng
2026-05-18  9:45   ` Biju Das
2026-05-19  2:38 ` [PATCH v2 0/2] Add Meta Rainiera6 BMC support Neil Cheng
2026-05-19  2:38   ` [PATCH v2 1/2] dt-bindings: arm: aspeed: Add Meta Rainiera6 board Neil Cheng
2026-05-19  2:38   ` [PATCH v2 2/2] ARM: dts: aspeed: rainiera6: Add Meta Rainiera6 BMC Neil Cheng
2026-05-27  2:06   ` Andrew Jeffery [this message]
2026-05-27  2:30   ` [PATCH v2 0/2] Add Meta Rainiera6 BMC support Andrew Jeffery

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=e059b59ecb9b0912ae8a044e3f745450b7095573.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --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=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=neilcheng0417@gmail.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
all inboxes | Powered by JetHome®