Linux Input/HID development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: VegetablCat <vegetablecat@foxmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	vegetablecat <vegetablecat@foxmail.com>
Subject: Re: [PATCH v2] Input: xpad - add support for Beitong KP series controllers
Date: Sat, 15 Aug 2026 18:29:24 +0800	[thread overview]
Message-ID: <202608151844.kqZOpOOS-lkp@intel.com> (raw)
In-Reply-To: <tencent_CD9DBF098D1B3BB565A1DD5761C1D34F4805@qq.com>

Hi VegetablCat,

kernel test robot noticed the following build errors:

[auto build test ERROR on dtor-input/next]
[also build test ERROR on dtor-input/for-linus hid/for-next linus/master v7.2-rc7 next-20260813]
[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/VegetablCat/Input-xpad-add-support-for-Beitong-KP-series-controllers/20260814-093918
base:   https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
patch link:    https://lore.kernel.org/r/tencent_CD9DBF098D1B3BB565A1DD5761C1D34F4805%40qq.com
patch subject: [PATCH v2] Input: xpad - add support for Beitong KP series controllers
config: m68k-randconfig-r071-20260815 (https://download.01.org/0day-ci/archive/20260815/202608151844.kqZOpOOS-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 16.1.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260815/202608151844.kqZOpOOS-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/202608151844.kqZOpOOS-lkp@intel.com/

All errors (new ones prefixed by >>):

   m68k-linux-ld: drivers/input/joystick/xpad.o: in function `xpad_receiver_remove':
>> xpad.c:(.text+0xa): undefined reference to `hid_hw_close'
>> m68k-linux-ld: xpad.c:(.text+0x18): undefined reference to `hid_hw_stop'
   m68k-linux-ld: drivers/input/joystick/xpad.o: in function `xpad_receiver_probe':
>> xpad.c:(.text+0x288): undefined reference to `hid_open_report'
>> m68k-linux-ld: xpad.c:(.text+0x29e): undefined reference to `hid_hw_start'
>> m68k-linux-ld: xpad.c:(.text+0x2ae): undefined reference to `hid_hw_open'
   m68k-linux-ld: xpad.c:(.text+0x2c2): undefined reference to `hid_hw_stop'
   m68k-linux-ld: drivers/input/joystick/xpad.o: in function `xpad_init':
>> xpad.c:(.init.text+0x12): undefined reference to `__hid_register_driver'
>> m68k-linux-ld: xpad.c:(.init.text+0x46): undefined reference to `hid_unregister_driver'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2026-08-15 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26  8:21 [PATCH v2] Input: xpad - add support for Beitong KP series controllers VegetablCat
2026-07-26  8:29 ` sashiko-bot
2026-08-15 10:29 ` kernel test robot [this message]

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=202608151844.kqZOpOOS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vegetablecat@foxmail.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