From: Shawn Guo <shawnguo@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [shawnguo:imx/dt64 61/65] include/vdso/bits.h:7:33: warning: excess elements in struct initializer
Date: Fri, 17 Dec 2021 11:08:35 +0800 [thread overview]
Message-ID: <20211217030835.GO4216@dragon> (raw)
In-Reply-To: <CAHCN7xKMQ_YvyVf_pMCYhOikuOW7tRD1wW_Yb65PQF4b5VH-3A@mail.gmail.com>
On Thu, Dec 16, 2021 at 04:46:34PM -0600, Adam Ford wrote:
> This was added in
> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/?h=for-next&id=042b67799e2991e301df8269e166d8bc5944495e
>
> The branch called imx/dt64 appears to be missing this, but it is
> present in the for-next branch. Is it possible to have the
> auto-builder use for-next as the base?
>
> I would expect it to work then.
My fault. Patches were applied to the wrong branch. Fixed now.
Shawn
> On Thu, Dec 16, 2021 at 4:07 PM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git imx/dt64
> > head: 99aa299322718d46f1d9f0552231c8eab5ec7f9c
> > commit: 31d517ab0a3cb40e11c5400ef0ec393e4a34db65 [61/65] soc: imx: imx8m-blk-ctrl: add i.MX8MN DISP blk-ctrl
> > config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20211217/202112170542.njccjabE-lkp@intel.com/config)
> > compiler: alpha-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://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/?id=31d517ab0a3cb40e11c5400ef0ec393e4a34db65
> > git remote add shawnguo https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git
> > git fetch --no-tags shawnguo imx/dt64
> > git checkout 31d517ab0a3cb40e11c5400ef0ec393e4a34db65
> > # 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=alpha SHELL=/bin/bash drivers/soc/imx/
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > drivers/soc/imx/imx8m-blk-ctrl.c:536:18: error: 'const struct imx8m_blk_ctrl_domain_data' has no member named 'mipi_phy_rst_mask'
> > 536 | .mipi_phy_rst_mask = BIT(17),
> > | ^~~~~~~~~~~~~~~~~
> > In file included from include/linux/bits.h:6,
> > from include/linux/ratelimit_types.h:5,
> > from include/linux/ratelimit.h:5,
> > from include/linux/dev_printk.h:16,
> > from include/linux/device.h:15,
> > from drivers/soc/imx/imx8m-blk-ctrl.c:7:
> > >> include/vdso/bits.h:7:33: warning: excess elements in struct initializer
> > 7 | #define BIT(nr) (UL(1) << (nr))
> > | ^
> > drivers/soc/imx/imx8m-blk-ctrl.c:536:38: note: in expansion of macro 'BIT'
> > 536 | .mipi_phy_rst_mask = BIT(17),
> > | ^~~
> > include/vdso/bits.h:7:33: note: (near initialization for 'imx8mn_disp_blk_ctl_domain_data[0]')
> > 7 | #define BIT(nr) (UL(1) << (nr))
> > | ^
> > drivers/soc/imx/imx8m-blk-ctrl.c:536:38: note: in expansion of macro 'BIT'
> > 536 | .mipi_phy_rst_mask = BIT(17),
> > | ^~~
> > drivers/soc/imx/imx8m-blk-ctrl.c:545:18: error: 'const struct imx8m_blk_ctrl_domain_data' has no member named 'mipi_phy_rst_mask'
> > 545 | .mipi_phy_rst_mask = BIT(16),
> > | ^~~~~~~~~~~~~~~~~
> > In file included from include/linux/bits.h:6,
> > from include/linux/ratelimit_types.h:5,
> > from include/linux/ratelimit.h:5,
> > from include/linux/dev_printk.h:16,
> > from include/linux/device.h:15,
> > from drivers/soc/imx/imx8m-blk-ctrl.c:7:
> > >> include/vdso/bits.h:7:33: warning: excess elements in struct initializer
> > 7 | #define BIT(nr) (UL(1) << (nr))
> > | ^
> > drivers/soc/imx/imx8m-blk-ctrl.c:545:38: note: in expansion of macro 'BIT'
> > 545 | .mipi_phy_rst_mask = BIT(16),
> > | ^~~
> > include/vdso/bits.h:7:33: note: (near initialization for 'imx8mn_disp_blk_ctl_domain_data[1]')
> > 7 | #define BIT(nr) (UL(1) << (nr))
> > | ^
> > drivers/soc/imx/imx8m-blk-ctrl.c:545:38: note: in expansion of macro 'BIT'
> > 545 | .mipi_phy_rst_mask = BIT(16),
> > | ^~~
> >
> >
> > vim +7 include/vdso/bits.h
> >
> > 3945ff37d2f48d3 Vincenzo Frascino 2020-03-20 6
> > 3945ff37d2f48d3 Vincenzo Frascino 2020-03-20 @7 #define BIT(nr) (UL(1) << (nr))
> > 3945ff37d2f48d3 Vincenzo Frascino 2020-03-20 8
> >
> > :::::: The code at line 7 was first introduced by commit
> > :::::: 3945ff37d2f48d39fd1751d282c80176654049e4 linux/bits.h: Extract common header for vDSO
> >
> > :::::: TO: Vincenzo Frascino <vincenzo.frascino@arm.com>
> > :::::: CC: Thomas Gleixner <tglx@linutronix.de>
> >
> > ---
> > 0-DAY CI Kernel Test Service, Intel Corporation
> > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-12-17 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 22:06 [shawnguo:imx/dt64 61/65] include/vdso/bits.h:7:33: warning: excess elements in struct initializer kernel test robot
2021-12-16 22:46 ` Adam Ford
2021-12-17 3:08 ` Shawn Guo [this message]
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=20211217030835.GO4216@dragon \
--to=shawnguo@kernel.org \
--cc=aford173@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.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