From: kernel test robot <lkp@intel.com>
To: Crystal Guo <crystal.guo@mediatek.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH 1/2] memory/mediatek: Add an interface to get current DDR data rate
Date: Sat, 21 Dec 2024 09:42:42 +0800 [thread overview]
Message-ID: <202412210955.FvO0Pee3-lkp@intel.com> (raw)
In-Reply-To: <20241212090029.13692-2-crystal.guo@mediatek.com>
Hi Crystal,
kernel test robot noticed the following build errors:
[auto build test ERROR on krzk-mem-ctrl/for-next]
[also build test ERROR on robh/for-next krzk-dt/for-next linus/master v6.13-rc3 next-20241220]
[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/Crystal-Guo/memory-mediatek-Add-an-interface-to-get-current-DDR-data-rate/20241212-170306
base: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git for-next
patch link: https://lore.kernel.org/r/20241212090029.13692-2-crystal.guo%40mediatek.com
patch subject: [PATCH 1/2] memory/mediatek: Add an interface to get current DDR data rate
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20241221/202412210955.FvO0Pee3-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241221/202412210955.FvO0Pee3-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/202412210955.FvO0Pee3-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/memory/mediatek/mtk-dramc.c:300:19: error: initialization of 'void (*)(struct platform_device *)' from incompatible pointer type 'int (*)(struct platform_device *)' [-Wincompatible-pointer-types]
300 | .remove = dramc_remove,
| ^~~~~~~~~~~~
drivers/memory/mediatek/mtk-dramc.c:300:19: note: (near initialization for 'dramc_drv.<anonymous>.remove')
vim +300 drivers/memory/mediatek/mtk-dramc.c
297
298 static struct platform_driver dramc_drv = {
299 .probe = dramc_probe,
> 300 .remove = dramc_remove,
301 .driver = {
302 .name = "dramc_drv",
303 .owner = THIS_MODULE,
304 .of_match_table = dramc_of_ids,
305 },
306 };
307
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-21 1:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 8:59 [PATCH 0/2] Add MediaTek DRAMC driver support Crystal Guo
2024-12-12 8:59 ` [PATCH 1/2] memory/mediatek: Add an interface to get current DDR data rate Crystal Guo
2024-12-12 10:46 ` AngeloGioacchino Del Regno
2025-02-08 4:14 ` Crystal Guo (郭晶)
2025-02-11 12:13 ` Crystal Guo (郭晶)
2024-12-12 11:02 ` Krzysztof Kozlowski
2025-02-08 4:21 ` Crystal Guo (郭晶)
2025-02-11 12:21 ` Crystal Guo (郭晶)
2024-12-21 1:42 ` kernel test robot [this message]
2024-12-21 11:03 ` kernel test robot
2024-12-12 8:59 ` [PATCH 2/2] dt-bindings: memory-controllers: Add mediatek common-dramc dt-bindings Crystal Guo
2024-12-12 10:27 ` Rob Herring (Arm)
2025-02-08 4:24 ` Crystal Guo (郭晶)
2024-12-12 10:27 ` AngeloGioacchino Del Regno
2025-02-08 4:33 ` Crystal Guo (郭晶)
2025-02-11 12:46 ` Crystal Guo (郭晶)
2024-12-12 10:58 ` Krzysztof Kozlowski
2025-02-08 4:40 ` Crystal Guo (郭晶)
2025-02-09 10:52 ` Krzysztof Kozlowski
2025-02-11 12:59 ` Crystal Guo (郭晶)
2025-02-11 15:57 ` Krzysztof Kozlowski
2025-02-12 3:21 ` Crystal Guo (郭晶)
2025-02-11 12:56 ` Crystal Guo (郭晶)
2025-02-11 15:55 ` Krzysztof Kozlowski
2025-02-12 2:47 ` Crystal Guo (郭晶)
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=202412210955.FvO0Pee3-lkp@intel.com \
--to=lkp@intel.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=crystal.guo@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@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