From: Stephen Boyd <sboyd@kernel.org>
To: Garmin.Chang <Garmin.Chang@mediatek.com>,
kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [clk:clk-mediatek 81/82] FATAL: modpost: drivers/clk/mediatek/clk-mt8188-imp_iic_wrap: sizeof(struct platform_device_id)=24 is not a modulo of the size of section __mod_platform__<identifier>_device_table=784.
Date: Mon, 03 Apr 2023 17:23:55 -0700 [thread overview]
Message-ID: <685a52da2ff0ba632da3ad033bb8b165.sboyd@kernel.org> (raw)
In-Reply-To: <202304020649.QO2HlpD5-lkp@intel.com>
Quoting kernel test robot (2023-04-01 16:05:54)
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-mediatek
> head: 0d2f2cefba64729a0730ce183ad58cf3e7929b94
> commit: 1b5e5299dd35da0dff2d454826a60870237837da [81/82] clk: mediatek: Add MT8188 imp i2c wrapper clock support
> config: parisc-randconfig-m041-20230402 (https://download.01.org/0day-ci/archive/20230402/202304020649.QO2HlpD5-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/commit/?id=1b5e5299dd35da0dff2d454826a60870237837da
> git remote add clk https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> git fetch --no-tags clk clk-mediatek
> git checkout 1b5e5299dd35da0dff2d454826a60870237837da
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202304020649.QO2HlpD5-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> >> FATAL: modpost: drivers/clk/mediatek/clk-mt8188-imp_iic_wrap: sizeof(struct platform_device_id)=24 is not a modulo of the size of section __mod_platform__<identifier>_device_table=784.
> Fix definition of struct platform_device_id in mod_devicetable.h
>
I suspect we need to include the header for mod_devicetable.h
_______________________________________________
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-04-04 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 23:05 [clk:clk-mediatek 81/82] FATAL: modpost: drivers/clk/mediatek/clk-mt8188-imp_iic_wrap: sizeof(struct platform_device_id)=24 is not a modulo of the size of section __mod_platform__<identifier>_device_table=784 kernel test robot
2023-04-04 0:23 ` Stephen Boyd [this message]
2023-04-04 4:44 ` Stephen Boyd
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=685a52da2ff0ba632da3ad033bb8b165.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=Garmin.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).