From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "J, KEERTHY" <j-keerthy@ti.com>,
robh+dt@kernel.org, rui.zhang@intel.com, amitk@kernel.org,
kristo@kernel.org, vigneshr@ti.com,
krzysztof.kozlowski@linaro.org
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 4/4] thermal: k3_j72xx_bandgap: Add the bandgap driver support
Date: Tue, 10 May 2022 19:38:03 +0200 [thread overview]
Message-ID: <76e12c64-9e87-d407-0676-3fa2955c3680@linaro.org> (raw)
In-Reply-To: <ffafc50e-9adb-9d66-3d1f-4ebc9f91f47d@ti.com>
On 10/05/2022 19:17, J, KEERTHY wrote:
>
[ ... ]
> Hi Daniel,
>
> Patch 1 & 4 i.e Documentation patch and driver patch can be picked by
> you. I believe Vignesh will take the dts patches.
Will you send a V7 with Krzysztof comments fixed ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-05-10 17:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:46 [PATCH v6 0/4] " Keerthy
2022-04-27 6:46 ` [PATCH v6 1/4] dt-bindings: thermal: k3-j72xx: Add VTM bindings documentation Keerthy
2022-05-03 0:34 ` Rob Herring
2022-05-09 3:18 ` J, KEERTHY
2022-05-09 6:42 ` Krzysztof Kozlowski
2022-05-11 7:53 ` J, KEERTHY
2022-05-11 8:15 ` Krzysztof Kozlowski
2022-05-11 10:57 ` J, KEERTHY
2022-04-27 6:46 ` [PATCH v6 2/4] arm64: dts: ti: j721e: Add VTM node Keerthy
2022-04-27 6:46 ` [PATCH v6 3/4] arm64: dts: ti: j7200: " Keerthy
2022-04-27 6:46 ` [PATCH v6 4/4] thermal: k3_j72xx_bandgap: Add the bandgap driver support Keerthy
2022-05-04 8:00 ` Dan Carpenter
2022-05-09 5:20 ` Joe Perches
2022-05-09 3:10 ` J, KEERTHY
2022-05-10 15:25 ` Daniel Lezcano
2022-05-10 17:17 ` J, KEERTHY
2022-05-10 17:38 ` Daniel Lezcano [this message]
2022-05-11 4:57 ` Vignesh Raghavendra
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=76e12c64-9e87-d407-0676-3fa2955c3680@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®