From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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 input tree
Date: Mon, 24 Oct 2022 22:02:22 -0700 [thread overview]
Message-ID: <Y1dt3gwcG6lSpQg7@google.com> (raw)
In-Reply-To: <20221025100048.49384530@canb.auug.org.au>
On Tue, Oct 25, 2022 at 10:00:48AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the input tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/input/keyboard/stmpe-keypad.c: In function 'stmpe_keypad_probe':
> drivers/input/keyboard/stmpe-keypad.c:353:9: error: implicit declaration of function 'of_property_read_u32' [-Werror=implicit-function-declaration]
> 353 | of_property_read_u32(np, "debounce-interval", &keypad->debounce_ms);
> | ^~~~~~~~~~~~~~~~~~~~
> drivers/input/keyboard/stmpe-keypad.c:355:33: error: implicit declaration of function 'of_property_read_bool' [-Werror=implicit-function-declaration]
> 355 | keypad->no_autorepeat = of_property_read_bool(np, "st,no-autorepeat");
> | ^~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 8b96465c93a8 ("Input: matrix_keypad - replace header inclusions by forward declarations")
>
> I have used the input tree from next-20221024 for today.
Thanks, I'll fix this up.
--
Dmitry
next prev parent reply other threads:[~2022-10-25 5:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 23:00 linux-next: build failure after merge of the input tree Stephen Rothwell
2022-10-25 5:02 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 0:00 Stephen Rothwell
2022-08-17 0:07 ` Stephen Rothwell
2022-08-17 4:43 ` Uwe Kleine-König
2022-08-01 21:44 broonie
2022-08-04 12:33 ` Mark Brown
2022-08-04 23:36 ` Jiri Kosina
2022-04-27 0:48 Stephen Rothwell
2022-04-27 6:53 ` Fabien Parent
2022-04-27 7:35 ` Lee Jones
2022-04-27 7:41 ` Fabien Parent
2022-05-02 2:17 ` Stephen Rothwell
2022-05-06 0:25 ` Dmitry Torokhov
2022-05-31 10:13 ` Fabien Parent
2020-03-25 7:16 Stephen Rothwell
2020-03-31 21:06 ` Stephen Rothwell
2015-10-16 2:19 Stephen Rothwell
2015-10-16 7:37 ` Hans de Goede
2015-10-17 16:39 ` Dmitry Torokhov
2015-07-24 1:49 Stephen Rothwell
2015-07-24 2:33 ` Dmitry Torokhov
2012-10-05 1:47 Stephen Rothwell
2012-10-05 6:12 ` Dmitry Torokhov
2012-01-24 3:25 Stephen Rothwell
2012-01-24 6:59 ` Dmitry Torokhov
2012-01-24 23:16 ` John Stultz
2010-08-19 1:35 Stephen Rothwell
2010-08-19 5:19 ` Dmitry Torokhov
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=Y1dt3gwcG6lSpQg7@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--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 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).