public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Qianfeng Rong <rongqianfeng@vivo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the i2c-host tree
Date: Fri, 4 Jul 2025 12:02:07 +1000	[thread overview]
Message-ID: <20250704120207.3e7d0d7e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

Hi all,

After merging the i2c-host tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

In file included from <command-line>:
drivers/i2c/busses/i2c-st.c: In function 'st_i2c_rd_fill_tx_fifo':
include/linux/compiler_types.h:568:45: error: call to '__compiletime_assert_369' declared with attribute error: min(max, 0x8 - tx_fstat) signedness error
  568 |         _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
      |                                             ^
include/linux/compiler_types.h:549:25: note: in definition of macro '__compiletime_assert'
  549 |                         prefix ## suffix();                             \
      |                         ^~~~~~
include/linux/compiler_types.h:568:9: note: in expansion of macro '_compiletime_assert'
  568 |         _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
      |         ^~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
   39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
      |                                     ^~~~~~~~~~~~~~~~~~
include/linux/minmax.h:93:9: note: in expansion of macro 'BUILD_BUG_ON_MSG'
   93 |         BUILD_BUG_ON_MSG(!__types_ok(ux, uy),           \
      |         ^~~~~~~~~~~~~~~~
include/linux/minmax.h:98:9: note: in expansion of macro '__careful_cmp_once'
   98 |         __careful_cmp_once(op, x, y, __UNIQUE_ID(x_), __UNIQUE_ID(y_))
      |         ^~~~~~~~~~~~~~~~~~
include/linux/minmax.h:105:25: note: in expansion of macro '__careful_cmp'
  105 | #define min(x, y)       __careful_cmp(min, x, y)
      |                         ^~~~~~~~~~~~~
drivers/i2c/busses/i2c-st.c:453:13: note: in expansion of macro 'min'
  453 |         i = min(max, SSC_TXFIFO_SIZE - tx_fstat);
      |             ^~~

Caused by commit

  cbae4d3dd2f7 ("i2c: busses: Use min() to improve code")

I have used the i2c-host tree from next-20250703 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-07-04  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04  2:02 Stephen Rothwell [this message]
2025-07-04  2:16 ` linux-next: build failure after merge of the i2c-host tree Qianfeng Rong
2025-07-04  2:36   ` Stephen Rothwell
2025-07-04  2:50     ` Qianfeng Rong
  -- strict thread matches above, loose matches on Subject: below --
2025-05-06  9:11 Stephen Rothwell
2025-05-06 11:47 ` Andi Shyti
2024-05-22  0:41 Stephen Rothwell
2024-05-22  5:33 ` Heiner Kallweit
2024-05-28  0:52   ` Stephen Rothwell
2024-05-28  1:01 ` Stephen Rothwell
2024-03-11 23:41 Stephen Rothwell
2024-03-12 10:44 ` Andi Shyti

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=20250704120207.3e7d0d7e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andi.shyti@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rongqianfeng@vivo.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