From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 4929/7613] ERROR: modpost: "__udivdi3" [net/openvswitch/openvswitch.ko] undefined!
Date: Fri, 08 May 2020 22:14:11 +0800 [thread overview]
Message-ID: <20200508141411.GM14816@intel.com> (raw)
In-Reply-To: <MW3PR11MB476447F8855F59B919CC1E2CE9A20@MW3PR11MB4764.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Fri, May 08, 2020 at 01:37:36PM +0000, Berg, Johannes wrote:
> Hi 0-day folks,
>
> > commit: d530b9864073a714a6b6dcddee77c9b24074071f [4929/7613] staging:
> > wilc1000: adjust for management frame register API changes
>
>
> > All errors (new ones prefixed by >>):
> >
> > >> ERROR: modpost: "__udivdi3" [net/openvswitch/openvswitch.ko]
> > undefined!
> > >> ERROR: modpost: "__divdi3" [net/openvswitch/openvswitch.ko]
> > undefined!
>
>
> Is there something wrong? Surely a change in a staging wireless driver didn't cause openvswitch to gain a 64/64 bit division ...
Hi Johannes, sorry for the noise, we will check this to fix
the problem.
>
> johannes
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Gary Kershaw
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
prev parent reply other threads:[~2020-05-08 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 12:45 [linux-next:master 4929/7613] ERROR: modpost: "__udivdi3" [net/openvswitch/openvswitch.ko] undefined! kbuild test robot
2020-05-08 13:37 ` Berg, Johannes
2020-05-08 14:14 ` Philip Li [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=20200508141411.GM14816@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.