From: kernel test robot <lkp@intel.com>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
NXP S32 Linux <s32@nxp.com>, Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>,
Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>,
Bogdan Hamciuc <bogdan.hamciuc@nxp.com>,
Ghennadi Procopciuc <Ghennadi.Procopciuc@nxp.com>
Subject: Re: [PATCH v5 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support
Date: Fri, 29 Nov 2024 05:18:02 +0800 [thread overview]
Message-ID: <202411290700.vbqI1pTY-lkp@intel.com> (raw)
In-Reply-To: <20241126114940.421143-3-ciprianmarian.costea@oss.nxp.com>
Hi Ciprian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on arm64/for-next/core linus/master v6.12]
[cannot apply to abelloni/rtc-next next-20241128]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ciprian-Costea/dt-bindings-rtc-add-schema-for-NXP-S32G2-S32G3-SoCs/20241128-100010
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20241126114940.421143-3-ciprianmarian.costea%40oss.nxp.com
patch subject: [PATCH v5 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20241129/202411290700.vbqI1pTY-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241129/202411290700.vbqI1pTY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411290700.vbqI1pTY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/rtc/rtc-s32g.c:109: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Convert a number of seconds to a value suitable for RTCVAL in our clock's
vim +109 drivers/rtc/rtc-s32g.c
107
108 /**
> 109 * Convert a number of seconds to a value suitable for RTCVAL in our clock's
110 * current configuration.
111 * @rtcval: The value to go into RTCVAL[RTCVAL]
112 * Returns: 0 for success, -EINVAL if @seconds push the counter past the
113 * 32bit register range
114 */
115 static int sec_to_rtcval(const struct rtc_priv *priv,
116 unsigned long seconds, u32 *rtcval)
117 {
118 u32 delta_cnt;
119
120 if (!seconds || seconds > cycles_to_sec(priv->rtc_hz, RTCCNT_MAX_VAL))
121 return -EINVAL;
122
123 /*
124 * RTCCNT is read-only; we must return a value relative to the
125 * current value of the counter (and hope we don't linger around
126 * too much before we get to enable the interrupt)
127 */
128 delta_cnt = seconds * priv->rtc_hz;
129 *rtcval = delta_cnt + ioread32(priv->rtc_base + RTCCNT_OFFSET);
130
131 return 0;
132 }
133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-28 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 11:49 [PATCH v5 0/4] add NXP RTC driver support for S32G2/S32G3 SoCs Ciprian Costea
2024-11-26 11:49 ` [PATCH v5 1/4] dt-bindings: rtc: add schema for NXP " Ciprian Costea
2024-11-26 19:08 ` Krzysztof Kozlowski
2024-11-27 12:01 ` Ciprian Marian Costea
2024-11-27 14:43 ` Rob Herring
2024-11-27 14:49 ` Ciprian Marian Costea
2024-11-26 11:49 ` [PATCH v5 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-11-26 18:05 ` Frank Li
2024-11-27 15:07 ` Ciprian Marian Costea
2024-11-27 15:32 ` Alexandre Belloni
2024-12-02 13:06 ` Ciprian Marian Costea
2024-11-28 21:18 ` kernel test robot [this message]
2024-11-26 11:49 ` [PATCH v5 3/4] arm64: defconfig: add S32G RTC module support Ciprian Costea
2024-11-26 11:49 ` [PATCH v5 4/4] MAINTAINERS: add NXP S32G RTC driver Ciprian Costea
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 11:44 [PATCH] mmc: sdhci-esdhc-imx: enable 'SDHCI_QUIRK_NO_LED' quirk for S32G Ciprian Costea
2024-11-26 11:44 ` [PATCH v5 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-11-30 20:07 ` kernel test robot
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=202411290700.vbqI1pTY-lkp@intel.com \
--to=lkp@intel.com \
--cc=Ghennadi.Procopciuc@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aruizrui@redhat.com \
--cc=bogdan.hamciuc@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=imx@lists.linux.dev \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=s32@nxp.com \
--cc=will@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