From: kernel test robot <lkp@intel.com>
To: Dipen Patel <dipenp@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: [arm-tegra:hte/for-next 7/10] drivers/gpio/gpiolib-cdev.c:851:41: error: passing argument 2 of 'hte_request_ts_ns' from incompatible pointer type
Date: Wed, 4 May 2022 11:14:19 +0800 [thread overview]
Message-ID: <202205041124.ou0h2qgO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git hte/for-next
head: cedbe14082d169f4c1136c70c5170a76bd9a076a
commit: 98935236600d4e179b664ffcfcd54e0ec3a1b4e3 [7/10] gpiolib: cdev: Add hardware timestamp clock type
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20220504/202205041124.ou0h2qgO-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git/commit/?id=98935236600d4e179b664ffcfcd54e0ec3a1b4e3
git remote add arm-tegra https://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git
git fetch --no-tags arm-tegra hte/for-next
git checkout 98935236600d4e179b664ffcfcd54e0ec3a1b4e3
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
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
vim +/hte_request_ts_ns +851 drivers/gpio/gpiolib-cdev.c
828
829 static int hte_edge_setup(struct line *line, u64 eflags)
830 {
831 int ret;
832 unsigned long flags = 0;
833 struct hte_ts_desc *hdesc = &line->hdesc;
834
835 if (eflags & GPIO_V2_LINE_FLAG_EDGE_RISING)
836 flags |= test_bit(FLAG_ACTIVE_LOW, &line->desc->flags) ?
837 HTE_FALLING_EDGE_TS : HTE_RISING_EDGE_TS;
838 if (eflags & GPIO_V2_LINE_FLAG_EDGE_FALLING)
839 flags |= test_bit(FLAG_ACTIVE_LOW, &line->desc->flags) ?
840 HTE_RISING_EDGE_TS : HTE_FALLING_EDGE_TS;
841
842 line->total_discard_seq = 0;
843
844 hte_init_line_attr(hdesc, desc_to_gpio(line->desc), flags,
845 NULL, line->desc);
846
847 ret = hte_ts_get(NULL, hdesc, 0);
848 if (ret)
849 return ret;
850
> 851 return hte_request_ts_ns(hdesc, process_hw_ts,
852 process_hw_ts_thread, line);
853 }
854
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-04 3:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202205041124.ou0h2qgO-lkp@intel.com \
--to=lkp@intel.com \
--cc=dipenp@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.com \
/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.