From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: kernel test robot <lkp@intel.com>,
bchihi@baylibre.com, rafael@kernel.org, amitk@kernel.org,
rui.zhang@intel.com
Cc: oe-kbuild-all@lists.linux.dev, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, khilman@baylibre.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, james.lo@mediatek.com,
rex-bc.chen@mediatek.com
Subject: Re: [PATCH v10 1/6] thermal/drivers/mediatek: Relocate driver to mediatek folder
Date: Fri, 13 Jan 2023 11:47:29 +0100 [thread overview]
Message-ID: <3dc0b861-04fe-317e-9c9a-39c238b71dd2@linaro.org> (raw)
In-Reply-To: <202301130353.wbXPctIq-lkp@intel.com>
On 12/01/2023 21:08, kernel test robot wrote:
[ ... ]
> All warnings (new ones prefixed by >>):
>
>>> drivers/thermal/mediatek/auxadc_thermal.c:562: warning: expecting prototype for raw_to_mcelsius(). Prototype was for raw_to_mcelsius_v1() instead
That has been fixed by:
https://lore.kernel.org/all/20230113064449.15061-1-rdunlap@infradead.org/
and applied in the thermal/linux-next branch
--
<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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-13 10:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:28 [PATCH v10 0/6] Add LVTS thermal architecture bchihi
2023-01-12 15:28 ` [PATCH v10 1/6] thermal/drivers/mediatek: Relocate driver to mediatek folder bchihi
[not found] ` <202301130353.wbXPctIq-lkp@intel.com>
2023-01-13 10:47 ` Daniel Lezcano [this message]
2023-01-12 15:28 ` [PATCH v10 2/6] dt-bindings/thermal/mediatek: Add dt-binding document for LVTS thermal controllers bchihi
2023-01-13 8:11 ` Krzysztof Kozlowski
2023-01-13 11:54 ` Matthias Brugger
2023-01-13 14:30 ` Balsam CHIHI
2023-01-16 10:38 ` AngeloGioacchino Del Regno
2023-01-16 11:05 ` Balsam CHIHI
2023-01-12 15:28 ` [PATCH v10 3/6] arm64/dts/mt8195: Add efuse node to mt8195 bchihi
2023-01-13 11:45 ` Matthias Brugger
2023-01-16 10:38 ` AngeloGioacchino Del Regno
2023-01-12 15:28 ` [PATCH v10 4/6] thermal/drivers/mediatek: Add the Low Voltage Thermal Sensor driver bchihi
2023-01-16 10:50 ` AngeloGioacchino Del Regno
2023-01-16 11:08 ` Daniel Lezcano
2023-01-16 11:52 ` AngeloGioacchino Del Regno
2023-01-18 13:58 ` Balsam CHIHI
2023-01-18 14:30 ` Daniel Lezcano
2023-01-18 14:52 ` Balsam CHIHI
2023-01-18 14:37 ` Balsam CHIHI
2023-01-12 15:28 ` [PATCH v10 5/6] arm64/dts/mt8195: Add thermal zones and thermal nodes bchihi
2023-01-12 15:28 ` [PATCH v10 6/6] arm64/dts/mt8195: Add temperature mitigation threshold bchihi
2023-01-13 11:49 ` Matthias Brugger
2023-01-13 14:24 ` Balsam CHIHI
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=3dc0b861-04fe-317e-9c9a-39c238b71dd2@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=bchihi@baylibre.com \
--cc=james.lo@mediatek.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rex-bc.chen@mediatek.com \
--cc=rui.zhang@intel.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