From: Rajaganesh Rathinasabapathi <rrathina@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rajaganesh Rathinasabapathi <Rajaganesh.Rathinasabapathi@amd.com>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
joel@jms.id.au, andrew@codeconstruct.com.au, robh+dt@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Subject: Re: [PATCH v3 2/2] ARM:dts:aspeed: Initial device tree for AMD Onyx Platform
Date: Tue, 18 Mar 2025 22:14:29 +0530 [thread overview]
Message-ID: <cfdbfe7e-5cf4-47a7-af5f-b220cad6f7e4@amd.com> (raw)
In-Reply-To: <20250318-imaginary-peccary-of-argument-ab6b39@krzk-bin>
On 3/18/25 14:15, Krzysztof Kozlowski wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Mon, Mar 17, 2025 at 11:12:24PM -0500, Rajaganesh Rathinasabapathi wrote:
>> +/ {
>> + model = "AMD Onyx BMC";
>> + compatible = "amd,onyx-bmc", "aspeed,ast2600";
>> +
>> + aliases {
>> + serial0 = &uart1;
>> + serial4 = &uart5;
>> + };
>> +
>> + chosen {
>> + stdout-path = serial4:115200n8;
>> + };
>> +
>> + memory@80000000 {
>> + device_type = "memory";
>> + reg = <0x80000000 0x80000000>;
>> + };
>> +
>> +};
>
> <form letter>
> This is a friendly reminder during the review process.
>
> It seems my or other reviewer's previous comments were not fully
> addressed. Maybe the feedback got lost between the quotes, maybe you
> just forgot to apply it. Please go back to the previous discussion and
> either implement all requested changes or keep discussing them.
>
> Thank you.
> </form letter>
>
> Best regards,
> Krzysztof
>
There were two comments. One was to remove bootargs, this is addressed in v3.
Another comment was to add compatibles for amd,onyx-bmc, it part of earlier commit (patch v3 1/2).
Thanks,
Raja
next prev parent reply other threads:[~2025-03-18 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 4:12 [PATCH v3 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Rajaganesh Rathinasabapathi
2025-03-18 4:12 ` [PATCH v3 2/2] ARM:dts:aspeed: Initial device tree for AMD Onyx Platform Rajaganesh Rathinasabapathi
2025-03-18 8:45 ` Krzysztof Kozlowski
2025-03-18 16:44 ` Rajaganesh Rathinasabapathi [this message]
2025-03-18 16:58 ` Krzysztof Kozlowski
2025-03-18 14:08 ` Andrew Lunn
2025-03-18 16:48 ` Rajaganesh Rathinasabapathi
2025-03-18 16:54 ` Andrew Lunn
2025-03-18 8:44 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: Add AMD Onyx BMC compatible Krzysztof Kozlowski
2025-03-18 16:42 ` Rajaganesh Rathinasabapathi
2025-03-18 16:43 ` Krzysztof Kozlowski
2025-03-18 16:43 ` Krzysztof Kozlowski
2025-03-18 17:07 ` Rob Herring (Arm)
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=cfdbfe7e-5cf4-47a7-af5f-b220cad6f7e4@amd.com \
--to=rrathina@amd.com \
--cc=Rajaganesh.Rathinasabapathi@amd.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=supreeth.venkatesh@amd.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