All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: Kristian Klausen <kristian@klausen.dk>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: drivers/platform/x86/asus-wmi.c:464: undefined reference to `battery_hook_unregister'
Date: Fri, 20 Sep 2019 12:59:13 +0300	[thread overview]
Message-ID: <20190920095913.GF2680@smile.fi.intel.com> (raw)
In-Reply-To: <201909201138.uyiNM7oj%lkp@intel.com>

On Fri, Sep 20, 2019 at 11:23:43AM +0800, kbuild test robot wrote:
> Hi Kristian,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   574cc4539762561d96b456dbc0544d8898bd4c6e
> commit: 7973353e92ee1e7ca3b2eb361a4b7cb66c92abee platform/x86: asus-wmi: Refactor charge threshold to use the battery hooking API
> date:   10 days ago
> config: x86_64-randconfig-e001-201937 (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
> reproduce:
>         git checkout 7973353e92ee1e7ca3b2eb361a4b7cb66c92abee
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):

The fix is on its way to linux-next followed by new PR to Linus within couple
of days.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2019-09-20  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20  3:23 drivers/platform/x86/asus-wmi.c:464: undefined reference to `battery_hook_unregister' kbuild test robot
2019-09-20  9:59 ` Andy Shevchenko [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=20190920095913.GF2680@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=kbuild-all@01.org \
    --cc=kristian@klausen.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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 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.