From: Christian Marangi <ansuelsmth@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the leds-lj tree
Date: Fri, 12 Jul 2024 09:48:41 +0200 [thread overview]
Message-ID: <6690dfdb.df0a0220.90a81.64f1@mx.google.com> (raw)
In-Reply-To: <20240712073139.GO501857@google.com>
On Fri, Jul 12, 2024 at 08:31:39AM +0100, Lee Jones wrote:
> Christian,
>
> > Hi all,
> >
> > After merging the leds-lj tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > In file included from drivers/leds/leds-lp5569.c:11:
> > drivers/leds/leds-lp5569.c: In function 'lp5569_post_init_device':
> > drivers/leds/leds-lp5569.c:204:52: error: passing argument 3 of 'lp55xx_read' from incompatible pointer type [-Werror=incompatible-pointer-types]
> > 204 | chip, LP5569_REG_STATUS, &val);
> > | ^~~~
> > | |
> > | int *
>
> The only reason for applying this set this late in the cycle was that
> they appeared to be fixes for other brokenness.
>
> This is the second set that you've submitted in recent days that has
> caused build breakages. Something is wrong with your current
> development practices. Are you able to identify and rectify these
> issue(s) before a lose trust in your submissions?
>
Yes, I identified the problem and the config was silently getting
disabled and hiding all the errors/warning. Driver also was tested on
OpenWrt build system where the option WERROR wasn't enabled as I was
devloping other stuff so this added on top of it of not noticing stuff.
I promise this won't ever happen again. Also I sent v2 for this hoping
things can get reverted and the correct series can be applied. If not I
can quickly send a followup that fix this. I verified with the repro
that the warning/error gets solved. (it's just channging the int to u8)
--
Ansuel
next prev parent reply other threads:[~2024-07-12 7:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 4:48 linux-next: build failure after merge of the leds-lj tree Stephen Rothwell
2024-07-12 7:31 ` Lee Jones
2024-07-12 7:48 ` Christian Marangi [this message]
2024-07-12 8:21 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 13:47 Mark Brown
2026-01-09 1:45 Stephen Rothwell
2026-01-09 9:41 ` Lee Jones
2026-01-19 18:56 ` Mark Brown
2026-01-20 8:46 ` Lee Jones
2026-01-26 22:00 ` Mark Brown
2026-02-02 14:56 ` Mark Brown
2026-02-03 18:26 ` Mark Brown
2026-02-04 9:21 ` Lee Jones
2025-03-21 4:52 Stephen Rothwell
2025-03-21 9:24 ` Lee Jones
2025-02-21 3:42 Stephen Rothwell
2024-07-10 6:34 Stephen Rothwell
2024-07-10 7:16 ` Lee Jones
2024-01-29 2:10 Stephen Rothwell
2024-01-31 8:56 ` Lee Jones
[not found] <20230809131733.67238c8a@canb.auug.org.au>
2023-08-09 12:53 ` Marek Vasut
2023-03-20 0:48 Stephen Rothwell
2023-03-20 1:00 ` ChiYuan Huang
2023-03-21 23:55 ` Stephen Rothwell
2023-03-22 15:28 ` Lee Jones
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=6690dfdb.df0a0220.90a81.64f1@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.