All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v4 4/6] ACPI / fan: Properly handle fine grain control
Date: Sat, 12 Feb 2022 06:46:17 +0800	[thread overview]
Message-ID: <202202120622.lPBqcxi6-lkp@intel.com> (raw)
In-Reply-To: <20220211160932.3221873-5-srinivas.pandruvada@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2764 bytes --]

Hi Srinivas,

I love your patch! Yet something to improve:

[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on linus/master v5.17-rc3 next-20220211]
[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]

url:    https://github.com/0day-ci/linux/commits/Srinivas-Pandruvada/ACPI-fan-Add-fine-grain-control/20220212-001118
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-a003 (https://download.01.org/0day-ci/archive/20220212/202202120622.lPBqcxi6-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/367e082b5f2d1c640b906682cffcb7195e722f26
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Srinivas-Pandruvada/ACPI-fan-Add-fine-grain-control/20220212-001118
        git checkout 367e082b5f2d1c640b906682cffcb7195e722f26
        # save the config file to linux build tree
        mkdir build_dir
        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 >>):

   ld: drivers/acpi/fan_core.o: in function `fan_get_state_acpi4':
>> drivers/acpi/fan_core.c:126: undefined reference to `__udivdi3'


vim +126 drivers/acpi/fan_core.c

   108	
   109	static int fan_get_state_acpi4(struct acpi_device *device, unsigned long *state)
   110	{
   111		struct acpi_fan *fan = acpi_driver_data(device);
   112		struct acpi_fan_fst fst;
   113		int status, i;
   114	
   115		status = acpi_fan_get_fst(device, &fst);
   116		if (status)
   117			return status;
   118	
   119		if (fan->fif.fine_grain_ctrl) {
   120			/* This control should be same what we set using _FSL by spec */
   121			if (fst.control > 100) {
   122				dev_dbg(&device->dev, "Invalid control value returned\n");
   123				goto match_fps;
   124			}
   125	
 > 126			*state = fst.control / fan->fif.step_size;
   127			return 0;
   128		}
   129	
   130	match_fps:
   131		for (i = 0; i < fan->fps_count; i++) {
   132			if (fst.control == fan->fps[i].control)
   133				break;
   134		}
   135		if (i == fan->fps_count) {
   136			dev_dbg(&device->dev, "Invalid control value returned\n");
   137			return -EINVAL;
   138		}
   139	
   140		*state = i;
   141	
   142		return status;
   143	}
   144	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  parent reply	other threads:[~2022-02-11 22:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 16:09 [PATCH v4 0/6] ACPI / fan: Add fine grain control Srinivas Pandruvada
2022-02-11 16:09 ` [PATCH v4 1/6] ACPI / fan: Fix error reporting to user space Srinivas Pandruvada
2022-02-11 16:09 ` [PATCH v4 2/6] ACPI / fan: Separate file for attributes creation Srinivas Pandruvada
2022-02-11 16:09 ` [PATCH v4 3/6] ACPI / fan: Optimize struct acpi_fan_fif Srinivas Pandruvada
2022-02-11 16:09 ` [PATCH v4 4/6] ACPI / fan: Properly handle fine grain control Srinivas Pandruvada
2022-02-11 22:15   ` kernel test robot
2022-02-11 22:46   ` kernel test robot [this message]
2022-02-11 16:09 ` [PATCH v4 5/6] ACPI / fan: Add additional attributes for " Srinivas Pandruvada
2022-02-11 16:09 ` [PATCH v4 6/6] Documentation/admin-guide/acpi: Add documentation " Srinivas Pandruvada

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=202202120622.lPBqcxi6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.