From: Krzysztof Kozlowski <krzk@kernel.org>
To: Willie Thai <wthai@nvidia.com>
Cc: andrew@codeconstruct.com.au, andrew@lunn.ch, conor+dt@kernel.org,
devicetree@vger.kernel.org, dkodihalli@nvidia.com,
gpiccoli@igalia.com, joel@jms.id.au, kees@kernel.org,
krzk+dt@kernel.org, leohu@nvidia.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org, maryang@nvidia.com,
openbmc@lists.ozlabs.org, pmenzel@molgen.mpg.de, robh@kernel.org,
tingkaic@nvidia.com, tony.luck@intel.com
Subject: Re: [PATCH v2] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC
Date: Wed, 19 Mar 2025 20:28:56 +0100 [thread overview]
Message-ID: <44f2387b-0a86-46cc-a5d2-950dd688b207@kernel.org> (raw)
In-Reply-To: <20250319112451.4171471-1-wthai@nvidia.com>
On 19/03/2025 12:24, Willie Thai wrote:
>>> +
>>> +// Enable Primary flash on FMC for bring up activity
>>> +&fmc {
>>> + status = "okay";
>>> + flash@0 {
>>> + status = "okay";
>>
>> Nothing improved.
>>
>> Respond to comment instead of ignoring it.
>>
>
> The property was disabled here: https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi#L172
I see, thanks.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-19 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 4:58 [PATCH v2] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC Willie Thai
2025-03-12 7:49 ` Krzysztof Kozlowski
2025-03-19 11:24 ` Willie Thai
2025-03-19 19:28 ` Krzysztof Kozlowski [this message]
2025-03-12 12:11 ` Andrew Lunn
2025-03-18 19:14 ` [PATCH v3] " Willie Thai
2025-03-12 13:07 ` [PATCH v2] " Rob Herring (Arm)
2025-03-20 10:02 ` Willie Thai
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=44f2387b-0a86-46cc-a5d2-950dd688b207@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=gpiccoli@igalia.com \
--cc=joel@jms.id.au \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maryang@nvidia.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh@kernel.org \
--cc=tingkaic@nvidia.com \
--cc=tony.luck@intel.com \
--cc=wthai@nvidia.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;
as well as URLs for NNTP newsgroup(s).