From: Krzysztof Kozlowski <krzk@kernel.org>
To: shunxi zhang <ot_shunxi.zhang@mediatek.com>,
alexandre.belloni@bootlin.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, lee@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/1] rtc: mediatek: Add mt6685 RTC driver
Date: Thu, 31 Oct 2024 16:59:51 +0100 [thread overview]
Message-ID: <a71058d1-47dc-4609-96ab-342d7617e05a@kernel.org> (raw)
In-Reply-To: <20241031135807.31605-1-ot_shunxi.zhang@mediatek.com>
On 31/10/2024 14:58, shunxi zhang wrote:
> From: Shunxi Zhang <ot_shunxi.zhang@mediatek.com>
>
> Signed-off-by: Shunxi Zhang <ot_shunxi.zhang@mediatek.com>
...
> +
> +static const struct mtk_rtc_data mt6685_rtc_data = {
> + .wrtgr = RTC_WRTGR,
> + .hwid = HWID_MT6685,
> + .chip_version = MT6685_SERIES,
> + .spare_reg_fields = mt6685_spare_reg_fields,
> + .cali_reg_fields = mt6685_cali_reg_fields,
> + .single_read_write_is_supported = true,
> +};
> +
> +static const struct of_device_id mt6685_rtc_of_match[] = {
> + { .compatible = "mediatek,mt6685-rtc", .data = &mt6685_rtc_data },
Please run scripts/checkpatch.pl and fix reported warnings. Then please
run `scripts/checkpatch.pl --strict` and (probably) fix more warnings.
Some warnings can be ignored, especially from --strict run, but the code
here looks like it needs a fix. Feel free to get in touch if the warning
is not clear.
You did not even run basic tools... I doubt that this was ever built
with W=1 and static checkers.
But above warning about undocumented ABI is a NAK.
Please run standard kernel tools for static analysis, like coccinelle,
smatch and sparse, and fix reported warnings. Also please check for
warnings when building with W=1. Most of these commands (checks or W=1
build) can build specific targets, like some directory, to narrow the
scope to only your code. The code here looks like it needs a fix. Feel
free to get in touch if the warning is not clear.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-31 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 13:58 [PATCH 1/1] rtc: mediatek: Add mt6685 RTC driver shunxi zhang
2024-10-31 15:58 ` Krzysztof Kozlowski
2024-10-31 16:05 ` Krzysztof Kozlowski
2024-12-27 10:44 ` Shunxi Zhang (章顺喜)
2024-10-31 15:59 ` Krzysztof Kozlowski [this message]
2024-10-31 17:24 ` Alexandre Belloni
2024-10-31 19:50 ` [PATCH] " Markus Elfring
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=a71058d1-47dc-4609-96ab-342d7617e05a@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_shunxi.zhang@mediatek.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).