From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Leo Wang <leo.jt.wang@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,
george.kw.lee@fii-foxconn.com, bruce.jy.hung@fii-foxconn.com,
leo.jt.wang@fii-foxconn.com
Subject: Re: [PATCH v2] ARM: dts: aspeed: clemente: add MCTP over I2C support
Date: Wed, 24 Sep 2025 11:46:55 +0930 [thread overview]
Message-ID: <e970c1693af3a612d9eccac2932e2e0be3d37453.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250922-leo-dts-transceiver-v2-1-d2dc0e24a70b@fii-foxconn.com>
Hi Leo,
On Mon, 2025-09-22 at 15:02 +0800, Leo Wang wrote:
> From: Leo Wang <leo.jt.wang@gmail.com>
>
> Enable MCTP communication on the Meta Clemente BMC board:
>
> - Add an MCTP I2C controller node at address 0x10 on I2C0
> - Mark selected I2C mux channels as MCTP controllers
> - Remove unused "i2c-mux-idle-disconnect" properties
>
> This allows MCTP devices to be discovered and used for
> management communication on the Clemente platform.
>
> Signed-off-by: Leo Wang <leo.jt.wang@gmail.com>
> ---
> Please consider the patch "[PATCH v1 1/1] ARM: dts: aspeed: clemente: add MCTP over I2C support"
> withdrawn.
>
> After further review we determined that enabling MCTP in the Clemente device-tree is not
> required; the affected devices are managed through other mechanisms and adding MCTP nodes
> would be unnecessary. To avoid confusion and noise, please ignore the previous patch.
>
> Original patch message-id: <20250918-leo-dts-transceiver-v1-1-3e2580325edc@gmail.com>
> ---
> Changes in v2:
> - Withdraw patch; no functional changes
> - Link to v1: https://lore.kernel.org/r/20250918-leo-dts-transceiver-v1-1-3e2580325edc@gmail.com
> ---
Please do not post a new revision of a series to announce withdrawal of
the series.
Rather, reply to the original series saying as much.
Thanks.
Andrew
prev parent reply other threads:[~2025-09-24 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 7:02 [PATCH v2] ARM: dts: aspeed: clemente: add MCTP over I2C support Leo Wang
2025-09-24 2:16 ` 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=e970c1693af3a612d9eccac2932e2e0be3d37453.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=bruce.jy.hung@fii-foxconn.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.kw.lee@fii-foxconn.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=leo.jt.wang@fii-foxconn.com \
--cc=leo.jt.wang@gmail.com \
--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