From: Jeremy Kerr <jk@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 06 May 2024 21:46:50 +0800 [thread overview]
Message-ID: <42ec2da02cc1260fd1c05bdeb620f770c8ecc767.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240506105120.3028083-1-dylan_hung@aspeedtech.com>
Hi Dylan,
> Add Aspeed AST2600 I3C controllers and add minimal changes to
> validate
> the functionality for MCTP-over-I3C.
>
> Dylan Hung (2):
> ? [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
I'd sent a similar patch earlier:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012193.html
And a v2 to account for some feedback on the dts layout:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012213.html
> ? [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
Looks interesting, I'll check this out soon.
Cheers,
Jeremy
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Dylan Hung <dylan_hung@aspeedtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-i3c@lists.infradead.org
Cc: BMC-SW@aspeedtech.com
Subject: Re: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 06 May 2024 21:46:50 +0800 [thread overview]
Message-ID: <42ec2da02cc1260fd1c05bdeb620f770c8ecc767.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240506105120.3028083-1-dylan_hung@aspeedtech.com>
Hi Dylan,
> Add Aspeed AST2600 I3C controllers and add minimal changes to
> validate
> the functionality for MCTP-over-I3C.
>
> Dylan Hung (2):
> [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
I'd sent a similar patch earlier:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012193.html
And a v2 to account for some feedback on the dts layout:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012213.html
> [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
Looks interesting, I'll check this out soon.
Cheers,
Jeremy
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Dylan Hung <dylan_hung@aspeedtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-i3c@lists.infradead.org
Cc: BMC-SW@aspeedtech.com
Subject: Re: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 06 May 2024 21:46:50 +0800 [thread overview]
Message-ID: <42ec2da02cc1260fd1c05bdeb620f770c8ecc767.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240506105120.3028083-1-dylan_hung@aspeedtech.com>
Hi Dylan,
> Add Aspeed AST2600 I3C controllers and add minimal changes to
> validate
> the functionality for MCTP-over-I3C.
>
> Dylan Hung (2):
> [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
I'd sent a similar patch earlier:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012193.html
And a v2 to account for some feedback on the dts layout:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012213.html
> [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
Looks interesting, I'll check this out soon.
Cheers,
Jeremy
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Dylan Hung <dylan_hung@aspeedtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-i3c@lists.infradead.org
Cc: BMC-SW@aspeedtech.com
Subject: Re: [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support
Date: Mon, 06 May 2024 21:46:50 +0800 [thread overview]
Message-ID: <42ec2da02cc1260fd1c05bdeb620f770c8ecc767.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240506105120.3028083-1-dylan_hung@aspeedtech.com>
Hi Dylan,
> Add Aspeed AST2600 I3C controllers and add minimal changes to
> validate
> the functionality for MCTP-over-I3C.
>
> Dylan Hung (2):
> [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs
I'd sent a similar patch earlier:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012193.html
And a v2 to account for some feedback on the dts layout:
https://lists.ozlabs.org/pipermail/linux-aspeed/2024-May/012213.html
> [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C
Looks interesting, I'll check this out soon.
Cheers,
Jeremy
next prev parent reply other threads:[~2024-05-06 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:51 [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` [PATCH 1/2] [RFC] ARM: dts: aspeed-g6: Add AST2600 I3Cs Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` [PATCH 2/2] [RFC] i3c: ast2600: Validate AST2600 I3C for MCTP-over-I3C Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 10:51 ` Dylan Hung
2024-05-06 13:46 ` Jeremy Kerr [this message]
2024-05-06 13:46 ` [PATCH 0/2] [RFC] i3c: ast2600: Add MCTP-over-I3C support Jeremy Kerr
2024-05-06 13:46 ` Jeremy Kerr
2024-05-06 13:46 ` Jeremy Kerr
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=42ec2da02cc1260fd1c05bdeb620f770c8ecc767.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=linux-aspeed@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.