From: kernel test robot <lkp@intel.com>
To: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>,
jikos@kernel.org, bentiss@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-input@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 10/10] HID: Add hid-universal-pidff driver and supported device ids
Date: Mon, 6 Jan 2025 14:28:41 +0800 [thread overview]
Message-ID: <202501061243.bXGf8kc8-lkp@intel.com> (raw)
In-Reply-To: <20250105193628.296350-11-tomasz.pakula.oficjalny@gmail.com>
Hi Tomasz,
kernel test robot noticed the following build errors:
[auto build test ERROR on hid/for-next]
[also build test ERROR on linus/master v6.13-rc6 next-20241220]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Tomasz-Paku-a/HID-pidff-Convert-infinite-length-from-Linux-API-to-PID-standard/20250106-033931
base: https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-next
patch link: https://lore.kernel.org/r/20250105193628.296350-11-tomasz.pakula.oficjalny%40gmail.com
patch subject: [PATCH v2 10/10] HID: Add hid-universal-pidff driver and supported device ids
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20250106/202501061243.bXGf8kc8-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250106/202501061243.bXGf8kc8-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501061243.bXGf8kc8-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/hid/hid-universal-pidff.c: In function 'universal_pidff_probe':
>> drivers/hid/hid-universal-pidff.c:90:23: error: assignment to 'void (*)(struct hid_device *, __u32)' {aka 'void (*)(struct hid_device *, unsigned int)'} from incompatible pointer type 'int (*)(struct hid_device *, __u32)' {aka 'int (*)(struct hid_device *, unsigned int)'} [-Wincompatible-pointer-types]
90 | init_function = hid_pidff_init_with_quirks;
| ^
>> drivers/hid/hid-universal-pidff.c:97:15: error: void value not ignored as it ought to be
97 | error = init_function(hdev, id->driver_data);
| ^
vim +90 drivers/hid/hid-universal-pidff.c
66
67
68 /*
69 * Check if the device is PID and initialize it
70 * Add quirks after initialisation
71 */
72 static int universal_pidff_probe(struct hid_device *hdev,
73 const struct hid_device_id *id)
74 {
75 int error;
76 error = hid_parse(hdev);
77 if (error) {
78 hid_err(hdev, "HID parse failed\n");
79 goto err;
80 }
81
82 error = hid_hw_start(hdev, HID_CONNECT_DEFAULT & ~HID_CONNECT_FF);
83 if (error) {
84 hid_err(hdev, "HID hw start failed\n");
85 goto err;
86 }
87
88 // Check if HID_PID support is enabled
89 void (*init_function)(struct hid_device *, __u32);
> 90 init_function = hid_pidff_init_with_quirks;
91
92 if (!init_function) {
93 hid_warn(hdev, "HID_PID support not enabled!\n");
94 return 0;
95 }
96
> 97 error = init_function(hdev, id->driver_data);
98 if (error) {
99 hid_warn(hdev, "Force Feedback initialization failed\n");
100 goto err;
101 }
102
103 hid_info(hdev, "Universal pidff driver loaded sucesfully!");
104
105 return 0;
106 err:
107 return error;
108 }
109
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-06 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241231154731.1719919-1-tomasz.pakula.oficjalny@gmail.com>
2025-01-05 19:36 ` [PATCH v2 00/10] HID: Upgrade the generic pidff driver and add hid-universal-pidff Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 01/10] HID: pidff: Convert infinite length from Linux API to PID standard Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 02/10] HID: pidff: Do not send effect envelope if it's empty Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 03/10] HID: pidff: Clamp PERIODIC effect period to device's logical range Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 04/10] HID: pidff: Add MISSING_DELAY quirk and its detection Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 05/10] HID: pidff: Add MISSING_PBO " Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 06/10] HID: pidff: Add MISSING_DEVICE_CONTROL quirk Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 07/10] HID: pidff: Add hid_pidff_init_with_quirks and export as GPL symbol Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 08/10] HID: pidff: Add FIX_WHEEL_DIRECTION quirk Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 09/10] HID: pidff: Stop all effects before enabling actuators Tomasz Pakuła
2025-01-05 19:36 ` [PATCH v2 10/10] HID: Add hid-universal-pidff driver and supported device ids Tomasz Pakuła
2025-01-06 6:28 ` kernel test robot [this message]
2025-01-06 18:26 ` kernel test robot
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=202501061243.bXGf8kc8-lkp@intel.com \
--to=lkp@intel.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tomasz.pakula.oficjalny@gmail.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 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).