linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Aleksa Savic <savicaleksa83@gmail.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: [linux-next:master 1554/3040] drivers/hwmon/aquacomputer_d5next.c:255: undefined reference to `crc16'
Date: Fri, 8 Apr 2022 17:11:43 +0800	[thread overview]
Message-ID: <202204081717.Ofq8vRMm-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   2e9a9857569ec27e64d2ddd01294bbe3c736acb1
commit: a5af7ccaf51299819dd0e5b1347d6f4d00752701 [1554/3040] hwmon: (aquacomputer_d5next) Add support for Aquacomputer Octo
config: microblaze-randconfig-r036-20220406 (https://download.01.org/0day-ci/archive/20220408/202204081717.Ofq8vRMm-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a5af7ccaf51299819dd0e5b1347d6f4d00752701
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout a5af7ccaf51299819dd0e5b1347d6f4d00752701
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=microblaze 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 >>):

   microblaze-linux-ld: drivers/hwmon/aquacomputer_d5next.o: in function `aqc_write':
>> drivers/hwmon/aquacomputer_d5next.c:255: undefined reference to `crc16'


vim +255 drivers/hwmon/aquacomputer_d5next.c

   247	
   248	/* Expects the mutex to be locked */
   249	static int aqc_send_ctrl_data(struct aqc_data *priv)
   250	{
   251		int ret;
   252		u16 checksum;
   253	
   254		/* Init and xorout value for CRC-16/USB is 0xffff */
 > 255		checksum = crc16(0xffff, priv->buffer + priv->checksum_start, priv->checksum_length);
   256		checksum ^= 0xffff;
   257	
   258		/* Place the new checksum at the end of the report */
   259		put_unaligned_be16(checksum, priv->buffer + priv->checksum_offset);
   260	
   261		/* Send the patched up report back to the device */
   262		ret = hid_hw_raw_request(priv->hdev, CTRL_REPORT_ID, priv->buffer, priv->buffer_size,
   263					 HID_FEATURE_REPORT, HID_REQ_SET_REPORT);
   264		if (ret < 0)
   265			return ret;
   266	
   267		/* The official software sends this report after every change, so do it here as well */
   268		ret = hid_hw_raw_request(priv->hdev, SECONDARY_CTRL_REPORT_ID, secondary_ctrl_report,
   269					 SECONDARY_CTRL_REPORT_SIZE, HID_FEATURE_REPORT,
   270					 HID_REQ_SET_REPORT);
   271		return ret;
   272	}
   273	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-04-08  9:12 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=202204081717.Ofq8vRMm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=savicaleksa83@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