From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrei Simion <andrei.simion@microchip.com>,
robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
mihai.sain@microchip.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: boot: dts: microchip: at91-sama7g5ek: Replace regulator-suspend-voltage with the valid property
Date: Tue, 2 Apr 2024 12:39:13 +0200 [thread overview]
Message-ID: <34543ae2-4e78-45a4-9cff-389f7495fd4a@linaro.org> (raw)
In-Reply-To: <20240402091228.110362-2-andrei.simion@microchip.com>
On 02/04/2024 11:12, Andrei Simion wrote:
> Replace regulator-suspend-voltage with regulator-suspend-microvolt.
Why?
Please explain what is the bug and how it manifests itself. Is one
property incorrect and other correct?
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching.
Hint: there is no "boot"
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-02 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 9:12 [PATCH 0/2] Fix the regulator-state-standby definition Andrei Simion
2024-04-02 9:12 ` [PATCH 1/2] ARM: boot: dts: microchip: at91-sama7g5ek: Replace regulator-suspend-voltage with the valid property Andrei Simion
2024-04-02 10:39 ` Krzysztof Kozlowski [this message]
2024-04-02 11:27 ` Andrei.Simion
2024-04-02 12:07 ` Krzysztof Kozlowski
2024-04-02 9:12 ` [PATCH 2/2] ARM: boot: dts: microchip: at91-sama7g54_curiosity: " Andrei Simion
2024-04-02 10:18 ` [PATCH 0/2] Fix the regulator-state-standby definition Nicolas Ferre
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=34543ae2-4e78-45a4-9cff-389f7495fd4a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andrei.simion@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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
all inboxes | Powered by JetHome®