Linux Input/HID development
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: kbuild-all@lists.01.org, linux-input@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>
Subject: [hid:for-next 11/27] drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c:48:9: error: implicit declaration of function 'writeq'; did you mean 'writeb'?
Date: Mon, 25 Jul 2022 08:19:49 +0800	[thread overview]
Message-ID: <202207250836.cwfTgngV-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-next
head:   9c9914cc509bccd7b134d33594e19b9411c12d4b
commit: 93ce5e0231d79189be4d9e5f9295807b18941419 [11/27] HID: amd_sfh: Implement SFH1.1 functionality
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20220725/202207250836.cwfTgngV-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.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/hid/hid.git/commit/?id=93ce5e0231d79189be4d9e5f9295807b18941419
        git remote add hid https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git
        git fetch --no-tags hid for-next
        git checkout 93ce5e0231d79189be4d9e5f9295807b18941419
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

Note: the hid/for-next HEAD 9c9914cc509bccd7b134d33594e19b9411c12d4b builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

   drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c: In function 'amd_stop_sensor':
>> drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c:48:9: error: implicit declaration of function 'writeq'; did you mean 'writeb'? [-Werror=implicit-function-declaration]
      48 |         writeq(0x0, privdata->mmio + AMD_C2P_MSG(1));
         |         ^~~~~~
         |         writeb
   cc1: some warnings being treated as errors


vim +48 drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c

    38	
    39	static void amd_stop_sensor(struct amd_mp2_dev *privdata, u16 sensor_idx)
    40	{
    41		struct sfh_cmd_base cmd_base;
    42	
    43		cmd_base.ul = 0;
    44		cmd_base.cmd.cmd_id = DISABLE_SENSOR;
    45		cmd_base.cmd.intr_disable = 0;
    46		cmd_base.cmd.sensor_id = sensor_idx;
    47	
  > 48		writeq(0x0, privdata->mmio + AMD_C2P_MSG(1));
    49		writel(cmd_base.ul, privdata->mmio + AMD_C2P_MSG(0));
    50	}
    51	

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

             reply	other threads:[~2022-07-25  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  0:19 kernel test robot [this message]
2022-07-25  9:40 ` [hid:for-next 11/27] drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c:48:9: error: implicit declaration of function 'writeq'; did you mean 'writeb'? Jiri Kosina
2022-07-25 15:44   ` Basavaraj Natikar
2022-07-25 15:50     ` Jiri Kosina

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=202207250836.cwfTgngV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=jkosina@suse.cz \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-input@vger.kernel.org \
    /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