From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dipen Patel <dipenp@nvidia.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 hte tree
Date: Wed, 4 May 2022 09:04:39 +0200 [thread overview]
Message-ID: <YnIlh++OJDRrK9sz@orome> (raw)
In-Reply-To: <20220504165956.531c4b53@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2501 bytes --]
On Wed, May 04, 2022 at 04:59:56PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hte tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpio/gpiolib-cdev.c:572:8: error: unknown type name 'hte_return_t'
> 572 | static hte_return_t process_hw_ts_thread(void *p)
> | ^~~~~~~~~~~~
> drivers/gpio/gpiolib-cdev.c:623:8: error: unknown type name 'hte_return_t'
> 623 | static hte_return_t process_hw_ts(struct hte_ts_data *ts, void *p)
> | ^~~~~~~~~~~~
> drivers/gpio/gpiolib-cdev.c: In function 'hte_edge_setup':
> drivers/gpio/gpiolib-cdev.c:851:41: error: passing argument 2 of 'hte_request_ts_ns' from incompatible pointer type [-Werror=incompatible-pointer-types]
> 851 | return hte_request_ts_ns(hdesc, process_hw_ts,
> | ^~~~~~~~~~~~~
> | |
> | int (*)(struct hte_ts_data *, void *)
> In file included from drivers/gpio/gpiolib-cdev.c:27:
> include/linux/hte.h:234:75: note: expected 'hte_ts_cb_t' {aka 'enum hte_return (*)(struct hte_ts_data *, void *)'} but argument is of type 'int (*)(struct hte_ts_data *, void *)'
> 234 | static inline int hte_request_ts_ns(struct hte_ts_desc *desc, hte_ts_cb_t cb,
> | ~~~~~~~~~~~~^~
> drivers/gpio/gpiolib-cdev.c:852:34: error: passing argument 3 of 'hte_request_ts_ns' from incompatible pointer type [-Werror=incompatible-pointer-types]
> 852 | process_hw_ts_thread, line);
> | ^~~~~~~~~~~~~~~~~~~~
> | |
> | int (*)(void *)
> In file included from drivers/gpio/gpiolib-cdev.c:27:
> include/linux/hte.h:235:53: note: expected 'hte_ts_sec_cb_t' {aka 'enum hte_return (*)(void *)'} but argument is of type 'int (*)(void *)'
> 235 | hte_ts_sec_cb_t tcb, void *data)
> | ~~~~~~~~~~~~~~~~^~~
> cc1: some warnings being treated as errors
>
> Something has been missed in the contruction of the git tree :-(
>
> I have dropped the hte tree for today.
Yeah, oddly I didn't catch that when I was doing the test build. Let me
recheck what went wrong there.
Sorry for the mess,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-04 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:59 linux-next: build failure after merge of the hte tree Stephen Rothwell
2022-05-04 7:04 ` Thierry Reding [this message]
2022-05-05 3:17 ` Dipen Patel
2022-05-05 14:04 ` Thierry Reding
2022-05-05 18:11 ` Dipen Patel
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=YnIlh++OJDRrK9sz@orome \
--to=thierry.reding@gmail.com \
--cc=dipenp@nvidia.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