From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: patrick@stwcx.xyz, Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Yosemite4: Add devices on I2C buses to server boards
Date: Thu, 19 Sep 2024 11:29:52 +0930 [thread overview]
Message-ID: <172671119203.649222.5621392370744640415.b4-ty@codeconstruct.com.au> (raw)
In-Reply-To: <20240910054751.2943217-1-Delphine_CC_Chiu@wiwynn.com>
On Tue, 10 Sep 2024 13:47:49 +0800, Delphine CC Chiu wrote:
> Changelog:
> - v1
> - Revise to use adm1281 on Medusa board.
> - Add gpio pca9506 for CPLD I/O expander.
>
> Ricky CX Wu (2):
> ARM: dts: aspeed: yosemite4: Revise to use adm1281 on Medusa board
> ARM: dts: aspeed: yosemite4: Add gpio pca9506 for CPLD IOE
>
> [...]
Thanks, I've applied this to be picked up through the BMC tree.
[1/2] ARM: dts: aspeed: yosemite4: Revise to use adm1281 on Medusa board
commit: 4c417a6b31471da78b87f9e542f285e2225744e0
[2/2] ARM: dts: aspeed: yosemite4: Add gpio pca9506 for CPLD IOE
commit: 00f897797acf562bcbda20d8ca93f279a0c6bb5b
--
Andrew Jeffery <andrew@codeconstruct.com.au>
prev parent reply other threads:[~2024-09-19 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 5:47 Delphine CC Chiu
2024-09-10 5:47 ` [PATCH v1 1/2] ARM: dts: aspeed: yosemite4: Revise to use adm1281 on Medusa board Delphine CC Chiu
2024-09-10 5:47 ` [PATCH v1 2/2] ARM: dts: aspeed: yosemite4: Add gpio pca9506 for CPLD IOE Delphine CC Chiu
2024-09-12 2:10 ` Andrew Jeffery
2024-09-13 2:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-13 3:26 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-16 3:05 ` Andrew Jeffery
2024-09-18 1:53 ` Ricky CX Wu/WYHQ/Wiwynn
2024-09-18 1:55 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2024-09-19 1:59 ` 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=172671119203.649222.5621392370744640415.b4-ty@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Delphine_CC_Chiu@wiwynn.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 \
/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®