public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Kevin Tung <kevin.tung.openbmc@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	 Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	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 v1 0/2] Add Meta (Facebook) Yosemite5 BMC (AST2600)
Date: Mon, 22 Sep 2025 12:17:12 +0930	[thread overview]
Message-ID: <7e6f568da28d7a63738b6ed22b33db3df4c478c9.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CABh9gBew1=hbJvg1Mhg5dE7Lr_Z442_kbBX6zTs_6_C2NRyLbw@mail.gmail.com>

On Thu, 2025-09-18 at 10:21 +0800, Kevin Tung wrote:
> On Wed, Sep 17, 2025 at 11:12 PM Andrew Lunn <andrew@lunn.ch> wrote:
> > 
> > On Wed, Sep 17, 2025 at 03:48:08PM +0800, Kevin Tung wrote:
> > > Summary:
> > > Add device tree for the Meta (Facebook) Yosemite5 compute node,
> > > based on the AST2600 BMC.
> > > 
> > > The Yosemite5 platform provides monitoring of voltages, power,
> > > temperatures, and other critical parameters across the motherboard,
> > > CXL board, E1.S expansion board, and NIC components. The BMC also
> > > logs relevant events and performs appropriate system actions in
> > > response to abnormal conditions.
> > > 
> > > Kevin Tung (2):
> > >   dt-bindings: arm: aspeed: add Meta Yosemite5 board
> > >   ARM: dts: aspeed: yosemite5: Add Meta Yosemite5 BMC
> > 
> > The threading between your patches are broken? How did you send them?
> > git send-email? b4 send?
> 
> Yes, the threading is broken. I initially used git send-email, but for
> some reason, only the cover letter was sent. I then sent the remaining
> dt-bindings and DTS patches separately as a follow-up.

I recommend using b4, it helps blunt some of the sharp edges of git-
send-email.

https://b4.docs.kernel.org/en/latest/

Can you please send v2 of the series so that it's properly threaded,
after applying tags you've collected for the involved patches, and
checking your work with `make CHECK_DTBS=y aspeed/aspeed-bmc-facebook-
yosemite5.dtb`?

Andrew


  reply	other threads:[~2025-09-22  2:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  7:48 [PATCH v1 0/2] Add Meta (Facebook) Yosemite5 BMC (AST2600) Kevin Tung
2025-09-17 15:12 ` Andrew Lunn
2025-09-18  2:21   ` Kevin Tung
2025-09-22  2:47     ` Andrew Jeffery [this message]
2025-09-24 13:04       ` Kevin Tung
2025-09-24 13:34         ` Rob Herring
2025-09-25  0:16           ` Andrew Jeffery
2025-10-01  8:54             ` Kevin Tung

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=7e6f568da28d7a63738b6ed22b33db3df4c478c9.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=joel@jms.id.au \
    --cc=kevin.tung.openbmc@gmail.com \
    --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=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