From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: ulcb-kf: document a problemw with old firmware
Date: Thu, 1 Feb 2024 10:32:23 +0100 [thread overview]
Message-ID: <ZbtlJ-7UCPxgUXeS@ninjato> (raw)
In-Reply-To: <CAMuHMdUB_9TNzo+GFbDZO-gjBUGfk7O7aEyJYG5pCw-Z1nK-pw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
Hi Geert,
> I'd rather not add such comments (especially +6y after the fact), as
> this is the standard operating procedure in case something doesn't work.
Okay, can be argued.
> /* If secondary CPUs don't work, please update your firmware */
> /* If cpuidle crashes, please update your firmware */
> /* If watchdog restart doesn't work, please update your firmware */
> /* If PSCI reboot doesn't work, please update your firmware */
Actually, I wouldn't mind. It documents that we *know* updating firmware
helps in this particular case. But as said, I can see your point as
well. Let's drop this patch.
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-01 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 9:52 [PATCH] arm64: dts: renesas: ulcb-kf: document a problemw with old firmware Wolfram Sang
2024-02-01 9:21 ` Geert Uytterhoeven
2024-02-01 9:32 ` Wolfram Sang [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=ZbtlJ-7UCPxgUXeS@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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