From: kernel test robot <lkp@intel.com>
To: Maxime Ripard <maxime@cerno.tech>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: kbuild-all@lists.01.org, dri-devel@lists.freedesktop.org,
linux-clk@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>,
Tim Gover <tim.gover@raspberrypi.com>,
Dom Cobley <dom@raspberrypi.com>,
Maxime Ripard <maxime@cerno.tech>,
kunit-dev@googlegroups.com
Subject: Re: [PATCH v5 01/11] clk: Introduce Kunit Tests for the framework
Date: Wed, 23 Feb 2022 10:25:14 +0800 [thread overview]
Message-ID: <202202231024.8SBLRlyr-lkp@intel.com> (raw)
In-Reply-To: <20220222131853.198625-2-maxime@cerno.tech>
Hi Maxime,
I love your patch! Yet something to improve:
[auto build test ERROR on clk/clk-next]
[also build test ERROR on next-20220217]
[cannot apply to drm-intel/for-linux-next drm-tip/drm-tip drm-exynos/exynos-drm-next drm/drm-next tegra-drm/drm/tegra/for-next linus/master airlied/drm-next v5.17-rc5]
[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]
url: https://github.com/0day-ci/linux/commits/Maxime-Ripard/clk-Improve-clock-range-handling/20220222-212043
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: mips-allmodconfig (https://download.01.org/0day-ci/archive/20220223/202202231024.8SBLRlyr-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/377d67441dca4a3d5df1d3b5a5b63c9a29f9b8b0
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Maxime-Ripard/clk-Improve-clock-range-handling/20220222-212043
git checkout 377d67441dca4a3d5df1d3b5a5b63c9a29f9b8b0
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "clk_hw_create_clk" [drivers/clk/clk_test.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-02-23 2:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:18 [PATCH v5 00/11] clk: Improve clock range handling Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 01/11] clk: Introduce Kunit Tests for the framework Maxime Ripard
2022-02-23 2:25 ` kernel test robot [this message]
2022-02-22 13:18 ` [PATCH v5 02/11] clk: Enforce that disjoints limits are invalid Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 03/11] clk: Always clamp the rounded rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 04/11] clk: Use clamp instead of open-coding our own Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 05/11] clk: Always set the rate on clk_set_range_rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 06/11] clk: Add clk_drop_range Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 07/11] clk: bcm: rpi: Add variant structure Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 08/11] clk: bcm: rpi: Set a default minimum rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 09/11] clk: bcm: rpi: Run some clocks at the minimum rate allowed Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 10/11] drm/vc4: Add logging and comments Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 11/11] drm/vc4: hdmi: Remove clock rate initialization Maxime Ripard
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=202202231024.8SBLRlyr-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dom@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-clk@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=phil@raspberrypi.com \
--cc=sboyd@kernel.org \
--cc=tim.gover@raspberrypi.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