From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: ERROR: modpost: "__mulsi3" undefined!
Date: Sun, 21 Jun 2020 14:45:50 +0800 [thread overview]
Message-ID: <20200621064550.GA11465@intel.com> (raw)
In-Reply-To: <2748b074-951c-000a-4d0a-780404e26dab@linux.com>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
On Sat, Jun 20, 2020 at 09:41:28AM +0300, Denis Efremov wrote:
>
>
> On 6/19/20 7:17 PM, kernel test robot wrote:
> > Hi Denis,
> >
> > First bad commit (maybe != root cause):
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 5e857ce6eae7ca21b2055cca4885545e29228fe2
> > commit: e4a42c82e943b97ce124539fcd7a47445b43fa0d kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables
> > date: 8 days ago
> > config: openrisc-randconfig-c022-20200619 (attached as .config)
> > compiler: or1k-linux-gcc (GCC) 9.3.0
> >
> > 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 >>, old ones prefixed by <<):
> >
>
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/pcf50633-charger.ko] undefined!
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/max17042_battery.ko] undefined!
> >>> ERROR: modpost: "__mulsi3" [drivers/power/supply/max17040_battery.ko] undefined!
>
> I'm not sure, but this report looks to me like the error was already in code before
> and the patch only rearranges the report.
sorry, this is a false positive report, kindly ignore it. We will resolve our
side logic issue in earliest time.
>
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/da9150-fg.ko] undefined!
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/bq27xxx_battery.ko] undefined!
>
>
> I found a similar reports:
> https://lkml.org/lkml/2020/6/19/341
> https://lkml.org/lkml/2019/12/11/2195
> https://lkml.org/lkml/2019/12/11/1977
>
> Thanks,
> Denis
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Philip Li <philip.li@intel.com>
To: Denis Efremov <efremov@linux.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [kbuild-all] Re: ERROR: modpost: "__mulsi3" undefined!
Date: Sun, 21 Jun 2020 14:45:50 +0800 [thread overview]
Message-ID: <20200621064550.GA11465@intel.com> (raw)
In-Reply-To: <2748b074-951c-000a-4d0a-780404e26dab@linux.com>
On Sat, Jun 20, 2020 at 09:41:28AM +0300, Denis Efremov wrote:
>
>
> On 6/19/20 7:17 PM, kernel test robot wrote:
> > Hi Denis,
> >
> > First bad commit (maybe != root cause):
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 5e857ce6eae7ca21b2055cca4885545e29228fe2
> > commit: e4a42c82e943b97ce124539fcd7a47445b43fa0d kbuild: fix broken builds because of GZIP,BZIP2,LZOP variables
> > date: 8 days ago
> > config: openrisc-randconfig-c022-20200619 (attached as .config)
> > compiler: or1k-linux-gcc (GCC) 9.3.0
> >
> > 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 >>, old ones prefixed by <<):
> >
>
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/pcf50633-charger.ko] undefined!
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/max17042_battery.ko] undefined!
> >>> ERROR: modpost: "__mulsi3" [drivers/power/supply/max17040_battery.ko] undefined!
>
> I'm not sure, but this report looks to me like the error was already in code before
> and the patch only rearranges the report.
sorry, this is a false positive report, kindly ignore it. We will resolve our
side logic issue in earliest time.
>
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/da9150-fg.ko] undefined!
> > ERROR: modpost: "__mulsi3" [drivers/power/supply/bq27xxx_battery.ko] undefined!
>
>
> I found a similar reports:
> https://lkml.org/lkml/2020/6/19/341
> https://lkml.org/lkml/2019/12/11/2195
> https://lkml.org/lkml/2019/12/11/1977
>
> Thanks,
> Denis
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
next prev parent reply other threads:[~2020-06-21 6:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 16:17 ERROR: modpost: "__mulsi3" undefined! kernel test robot
2020-06-19 16:17 ` kernel test robot
2020-06-20 6:41 ` Denis Efremov
2020-06-20 6:41 ` Denis Efremov
2020-06-21 6:45 ` Philip Li [this message]
2020-06-21 6:45 ` [kbuild-all] " Philip Li
-- strict thread matches above, loose matches on Subject: below --
2020-06-21 5:49 kernel test robot
2020-06-21 5:49 ` kernel test robot
2020-06-21 6:38 ` Philip Li
2020-06-21 3:35 kernel test robot
2020-06-21 3:35 ` kernel test robot
2020-06-21 5:42 ` Philip Li
2020-06-21 1:32 kernel test robot
2020-06-21 1:32 ` kernel test robot
2020-06-21 5:45 ` Philip Li
2020-06-21 0:58 kernel test robot
2020-06-21 0:58 ` kernel test robot
2020-06-21 5:45 ` Philip Li
2020-06-20 8:38 kernel test robot
2020-06-20 8:38 ` kernel test robot
2020-06-19 11:44 kernel test robot
2020-06-19 11:44 ` kernel test robot
2020-06-19 15:21 ` Philip Li
2020-06-19 11:10 kernel test robot
2020-06-19 11:10 ` kernel test robot
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=20200621064550.GA11465@intel.com \
--to=philip.li@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.