From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pavel Machek <pavel@ucw.cz>
Cc: Bernardo Rodrigues <bernardocrodrigues@live.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 leds tree
Date: Fri, 23 Sep 2022 14:31:38 +1000 [thread overview]
Message-ID: <20220923143138.71765678@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Hi all,
After merging the leds tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/leds/leds-pca963x.c: In function 'pca963x_register_leds':
drivers/leds/leds-pca963x.c:355:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
355 | if (hw_blink)
| ^~
drivers/leds/leds-pca963x.c:357:25: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
357 | led->blinking = false;
| ^~~
Caused by commit
fd6dd9584ed3 ("leds: pca963x: fix blink with hw acceleration")
I have used the version of the leds tree from next-20220921 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-09-23 4:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 4:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 20:53 linux-next: build failure after merge of the leds tree broonie
2022-09-26 21:18 ` Pavel Machek
2020-01-06 3:21 Stephen Rothwell
2020-01-06 9:31 ` Guido Günther
2020-01-06 10:32 ` Pavel Machek
2020-01-06 15:52 ` Guido Günther
2019-07-25 2:31 Stephen Rothwell
2019-07-25 18:44 ` Jacek Anaszewski
2013-06-17 5:29 Stephen Rothwell
2013-06-17 6:26 ` Alexander Shiyan
2013-06-21 0:16 ` Stephen Rothwell
2013-06-21 0:27 ` Grant Likely
2013-01-23 4:12 Stephen Rothwell
2013-01-23 6:05 ` Kim, Milo
2012-06-13 4:10 Stephen Rothwell
2012-06-13 4:25 ` Bryan Wu
2012-06-08 2:44 Stephen Rothwell
2012-06-08 3:33 ` Bryan Wu
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=20220923143138.71765678@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bernardocrodrigues@live.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).