mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: kernel test robot <lkp@intel.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: Re: include/linux/compiler_types.h:597:38: error: call to '__compiletime_assert_495' declared with attribute error: FIELD_PREP: value too large for the field
Date: Fri, 23 Jan 2026 11:15:35 +0100	[thread overview]
Message-ID: <c2f6eb5f-0eb6-47c4-9627-d2a5dfd6abd4@mailbox.org> (raw)
In-Reply-To: <202601230809.FBjF6OrH-lkp@intel.com>

On 1/23/26 1:58 AM, kernel test robot wrote:
> Hi Marek,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   a66191c590b3b58eaff05d2277971f854772bd5b
> commit: 4f716a1db661cfb31502a0a6d7e62c06daf2e603 drm/rcar-du: dsi: Convert register bitfields to GENMASK() macro
> date:   3 months ago
> config: arc-randconfig-r053-20260123 (https://download.01.org/0day-ci/archive/20260123/202601230809.FBjF6OrH-lkp@intel.com/config)
> compiler: arc-linux-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601230809.FBjF6OrH-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/202601230809.FBjF6OrH-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>     In file included from <command-line>:
>     drivers/gpu/drm/renesas/rcar-du/rcar_mipi_dsi.c: In function 'rcar_mipi_dsi_startup.isra.6':
>>> include/linux/compiler_types.h:597:38: error: call to '__compiletime_assert_495' declared with attribute error: FIELD_PREP: value too large for the field
>       _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>                                           ^
>     include/linux/compiler_types.h:578:4: note: in definition of macro '__compiletime_assert'
>         prefix ## suffix();    \
>         ^~~~~~
>     include/linux/compiler_types.h:597:2: note: in expansion of macro '_compiletime_assert'
>       _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>       ^~~~~~~~~~~~~~~~~~~
>     include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
>      #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
>                                          ^~~~~~~~~~~~~~~~~~
>     include/linux/bitfield.h:68:3: note: in expansion of macro 'BUILD_BUG_ON_MSG'
>        BUILD_BUG_ON_MSG(__builtin_constant_p(_val) ?  \
>        ^~~~~~~~~~~~~~~~
>     include/linux/bitfield.h:115:3: note: in expansion of macro '__BF_FIELD_CHECK'
>        __BF_FIELD_CHECK(_mask, 0ULL, _val, "FIELD_PREP: "); \
>        ^~~~~~~~~~~~~~~~
>     drivers/gpu/drm/renesas/rcar-du/rcar_mipi_dsi_regs.h:259:29: note: in expansion of macro 'FIELD_PREP'
>      #define VCLKSET_DIV_V4H(n)  FIELD_PREP(VCLKSET_DIV_V4H_MASK, (n))
>                                  ^~~~~~~~~~
>     drivers/gpu/drm/renesas/rcar-du/rcar_mipi_dsi.c:660:14: note: in expansion of macro 'VCLKSET_DIV_V4H'
>        vclkset |= VCLKSET_DIV_V4H(__ffs(setup_info.vclk_divider) - 1);
>                   ^~~~~~~~~~~~~~~

Hello Tomi, Laurent,

maybe it would be good to pick:

drm/rcar-du: dsi: Clean up VCLK divider calculation

that was posted about a month ago and fixes this exact warning ?

  reply	other threads:[~2026-01-23 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  0:58 kernel test robot
2026-01-23 10:15 ` Marek Vasut [this message]
2026-01-23 15:52   ` Laurent Pinchart

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=c2f6eb5f-0eb6-47c4-9627-d2a5dfd6abd4@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tomi.valkeinen+renesas@ideasonboard.com \
    --cc=tomi.valkeinen@ideasonboard.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

all inboxes | Powered by JetHome®