From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bartosz Golaszewski <brgl@bgdev•pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro•org>,
Dipen Patel <dipenp@nvidia•com>,
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: linux-next: build failure after merge of the gpio-brgl tree
Date: Fri, 13 Oct 2023 15:14:17 +1100 [thread overview]
Message-ID: <20231013151417.052aa2f5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Hi all,
After merging the gpio-brgl tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/hte/hte-tegra194.c: In function 'tegra_hte_line_xlate':
drivers/hte/hte-tegra194.c:424:48: error: implicit declaration of function 'gpio_device_get_base'; did you mean 'gpio_device_get_desc'? [-Werror=implicit-function-declaration]
424 | line_id = desc->attr.line_id - gpio_device_get_base(gs->gdev);
| ^~~~~~~~~~~~~~~~~~~~
| gpio_device_get_desc
drivers/hte/hte-tegra194.c: In function 'tegra_hte_match_from_linedata':
drivers/hte/hte-tegra194.c:652:33: error: implicit declaration of function 'gpiod_to_device'; did you mean 'gpio_to_desc'? [-Werror=implicit-function-declaration]
652 | gpiod_to_device(hdesc->attr.line_data);
| ^~~~~~~~~~~~~~~
| gpio_to_desc
drivers/hte/hte-tegra194.c:652:33: error: initialization of 'struct gpio_device *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
cc1: all warnings being treated as errors
Caused by commit
ebee532ff34b ("hte: tegra194: don't access struct gpio_chip")
(Exposed by commit
63137bee5a7a ("hte: allow building modules with COMPILE_TEST enabled")
from the hte tree.)
I have used the gpio-brgl tree from next-20231012 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-13 4:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 4:14 Stephen Rothwell [this message]
2023-10-13 6:44 ` linux-next: build failure after merge of the gpio-brgl tree Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 7:18 Stephen Rothwell
2025-10-20 0:56 Stephen Rothwell
2025-10-20 1:27 ` Stephen Rothwell
2025-10-17 14:47 Mark Brown
2025-10-17 14:52 ` Bartosz Golaszewski
2024-02-23 3:33 Stephen Rothwell
2024-02-23 7:51 ` Bartosz Golaszewski
2024-02-23 12:29 ` Andy Shevchenko
2024-02-25 1:58 ` Stephen Rothwell
2024-02-26 19:07 ` Bartosz Golaszewski
2023-03-23 1:29 Stephen Rothwell
2023-03-22 19:50 ` William Breathitt Gray
2023-03-23 13:32 ` Bartosz Golaszewski
2021-12-20 5:51 Stephen Rothwell
2021-12-20 12:46 ` Andy Shevchenko
2021-12-13 20:31 broonie
2021-12-14 3:12 ` Florian Fainelli
2021-12-17 6:17 ` Stephen Rothwell
2021-12-17 9:14 ` Bartosz Golaszewski
2021-11-15 23:51 Stephen Rothwell
2021-11-17 21:29 ` Rob Herring
2021-11-18 0:29 ` Stephen Rothwell
2021-11-23 2:04 ` Stephen Rothwell
2021-12-02 3:16 ` Stephen Rothwell
2021-02-18 6:54 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=20231013151417.052aa2f5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=bartosz.golaszewski@linaro$(echo .)org \
--cc=brgl@bgdev$(echo .)pl \
--cc=dipenp@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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