From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Kevin Tung <kevin.tung.openbmc@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>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Amithash Prasasd <amithash@meta.com>,
Kevin Tung <Kevin.Tung@quantatw.com>,
Ken Chen <Ken.Chen@quantatw.com>,
Leo Yang <Leo-Yang@quantatw.com>
Subject: Re: [PATCH v2 0/4] Revise Meta Yosemite5 devicetree
Date: Mon, 24 Nov 2025 15:23:14 +1030 [thread overview]
Message-ID: <c56ef6e76858c7df19ec43a3a18ccf79ff3cc489.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251120-yv5_revise_dts-v2-0-4d7de701c5be@gmail.com>
Hi Kevin,
On Thu, 2025-11-20 at 13:25 +0800, Kevin Tung wrote:
> Summary:
> Revise linux device tree entry related to Meta (Facebook) Yosemite5.
>
> Changes in v2:
> - Add ipmb node for OCP debug card
> - Link to v1: https://lore.kernel.org/r/20251118-yv5_revise_dts-v1-0-fcd6b44b4497@gmail.com
>
> Changes in v1:
> - Increase i2c4/i2c12 bus speed to 400 kHz
> - Update sensor configuration
> - Rename sgpio P0_I3C_APML_ALERT_L
Sorry, I replied with comments on v1 before I saw v2.
Can you please resolve the discussions on v1 and send a follow-up
series if necessary?
Andrew
next prev parent reply other threads:[~2025-11-24 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 5:25 Kevin Tung
2025-11-20 5:25 ` [PATCH v2 1/4] ARM: dts: aspeed: yosemite5: Increase i2c4/i2c12 bus speed to 400 kHz Kevin Tung
2025-11-20 5:25 ` [PATCH v2 2/4] ARM: dts: aspeed: yosemite5: Update sensor configuration Kevin Tung
2025-11-20 5:26 ` [PATCH v2 3/4] ARM: dts: aspeed: yosemite5: Rename sgpio P0_I3C_APML_ALERT_L Kevin Tung
2025-11-20 5:26 ` [PATCH v2 4/4] ARM: dts: aspeed: yosemite5: Add ipmb node for OCP debug card Kevin Tung
2025-11-24 4:53 ` Andrew Jeffery [this message]
2025-12-19 8:39 ` [PATCH v2 0/4] Revise Meta Yosemite5 devicetree 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=c56ef6e76858c7df19ec43a3a18ccf79ff3cc489.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Ken.Chen@quantatw.com \
--cc=Kevin.Tung@quantatw.com \
--cc=Leo-Yang@quantatw.com \
--cc=amithash@meta.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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®