From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz, amithash@meta.com,
Yang Chen <yangchen.openbmc@gmail.com>
Cc: Jerry.Lin@quantatw.com
Subject: Re: [PATCH v1 0/3] Revise Meta (Facebook) Minerva BMC (AST2600)
Date: Wed, 25 Sep 2024 10:14:58 +0930 [thread overview]
Message-ID: <172722509817.374662.7338401100529556748.b4-ty@codeconstruct.com.au> (raw)
In-Reply-To: <20240924140215.2484170-1-yangchen.openbmc@gmail.com>
On Tue, 24 Sep 2024 22:02:12 +0800, Yang Chen wrote:
> Revise linux device tree entry related to Meta (Facebook) Minerva specific
> devices connected to BMC (AST2600) SoC.
>
> Yang Chen (3):
> ARM: dts: aspeed: minerva: Revise the SGPIO line name
> ARM: dts: aspeed: minerva: change the i2c mux number for FCBs
> ARM: dts: aspeed: minerva: add fru device for other blades
>
> [...]
Thanks, I've applied this to be picked up through the BMC tree.
--
Andrew Jeffery <andrew@codeconstruct.com.au>
prev parent reply other threads:[~2024-09-25 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 14:02 Yang Chen
2024-09-24 14:02 ` [PATCH v1 1/3] ARM: dts: aspeed: minerva: Revise the SGPIO line name Yang Chen
2024-09-24 14:02 ` [PATCH v1 2/3] ARM: dts: aspeed: minerva: change the i2c mux number for FCBs Yang Chen
2024-09-24 14:02 ` [PATCH v1 3/3] ARM: dts: aspeed: minerva: add fru device for other blades Yang Chen
2024-09-25 0:44 ` Andrew Jeffery [this message]
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=172722509817.374662.7338401100529556748.b4-ty@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Jerry.Lin@quantatw.com \
--cc=amithash@meta.com \
--cc=conor+dt@kernel.org \
--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=robh@kernel.org \
--cc=yangchen.openbmc@gmail.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
all inboxes | Powered by JetHome®