From: Benjamin Bara <bbara93@gmail.com>
To: krzysztof.kozlowski@linaro.org
Cc: DLG-Adam.Thomson.Opensource@dm.renesas.com, bbara93@gmail.com,
benjamin.bara@skidata.com, broonie@kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
lee@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, mazziesaccount@gmail.com,
robh+dt@kernel.org, stwiss.opensource@diasemi.com,
support.opensource@diasemi.com
Subject: Re: [PATCH v3 3/3] dt-bindings: mfd: dlg,da9063: document voltage monitoring
Date: Thu, 6 Apr 2023 10:38:12 +0200 [thread overview]
Message-ID: <20230406083812.887582-1-bbara93@gmail.com> (raw)
In-Reply-To: <d7e795b8-6c36-70c5-73e4-ae115cac32a9@linaro.org>
On Thu, 6 Apr 2023 at 10:28, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> It looks like you received a tag and forgot to add it.
> If a tag was not added on purpose, please state why and what changed.
I slightly modified the description:
Basically clarified that both, uv and ov, must be set to the same severity and
value. I guess that wasn't very clear before.
I mentioned the change in the cover letter. Maybe I should have added it here
too, sorry for that.
Best regards,
Benjamin
next prev parent reply other threads:[~2023-04-06 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 17:14 [PATCH v3 0/3] regulator: da9063: disable unused voltage monitors Benjamin Bara
2023-04-05 17:14 ` [PATCH v3 1/3] regulator: da9063: add voltage monitoring registers Benjamin Bara
2023-04-05 17:14 ` [PATCH v3 2/3] regulator: da9063: implement setter for voltage monitoring Benjamin Bara
2023-04-05 17:14 ` [PATCH v3 3/3] dt-bindings: mfd: dlg,da9063: document " Benjamin Bara
2023-04-06 8:28 ` Krzysztof Kozlowski
2023-04-06 8:38 ` Benjamin Bara [this message]
2023-04-06 9:30 ` Krzysztof Kozlowski
2023-04-06 9:31 ` Krzysztof Kozlowski
2023-04-20 10:58 ` Lee Jones
2023-04-12 16:34 ` [PATCH v3 0/3] regulator: da9063: disable unused voltage monitors Mark Brown
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=20230406083812.887582-1-bbara93@gmail.com \
--to=bbara93@gmail.com \
--cc=DLG-Adam.Thomson.Opensource@dm.renesas.com \
--cc=benjamin.bara@skidata.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stwiss.opensource@diasemi.com \
--cc=support.opensource@diasemi.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).