From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Svyatoslav Ryhel <clamor95@gmail.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 extcon tree
Date: Tue, 6 May 2025 16:22:10 +1000 [thread overview]
Message-ID: <20250506162210.4a0b0139@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi all,
After merging the extcon tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/extcon/extcon-max14526.c: In function 'max14526_probe':
drivers/extcon/extcon-max14526.c:252:74: error: conversion from 'long unsigned int' to 'unsigned int' changes value from '18446744073709551614' to '4294967294' [-Werror=overflow]
252 | regmap_write_bits(priv->regmap, MAX14526_CONTROL_2, USB_DET_DIS, ~USB_DET_DIS);
cc1: all warnings being treated as errors
Caused by commit
0367e6929cf6 ("extcon: Add basic support for Maxim MAX14526 MUIC")
18446744073709551614 is 0xFFFFFFFFFFFFFFFE.
I have used the extcon tree from next-20250505 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-05-06 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 6:22 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-04 5:24 Stephen Rothwell
2024-09-04 9:24 ` Hans de Goede
2024-09-04 16:18 ` Chanwoo Choi
2019-07-19 0:48 Stephen Rothwell
2015-05-25 11:05 Stephen Rothwell
2015-06-04 9:18 ` Stephen Rothwell
2015-06-05 10:53 ` Greg KH
2015-06-27 0:16 ` Stephen Rothwell
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=20250506162210.4a0b0139@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=clamor95@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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
all inboxes | Powered by JetHome®