From: Kalle Valo <kvalo@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild test robot <lkp@intel.com>,
pillair@codeaurora.org, kbuild-all@01.org,
ath10k@lists.infradead.org, svishnoi@codeaurora.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath6kl:pending 10/15] ERROR: "__udivdi3" [drivers/net/wireless/ath/ath10k/ath10k_core.ko] undefined!
Date: Fri, 12 Oct 2018 17:49:37 +0300 [thread overview]
Message-ID: <878t3343um.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAK8P3a2NaKwHwe3RE_wZN6=myd1dqtWC91EJahbbKuS2oZ+xXw@mail.gmail.com> (Arnd Bergmann's message of "Fri, 12 Oct 2018 16:46:10 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Fri, Oct 12, 2018 at 4:32 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> + linux-wireless, arnd
>>
>> >
>> >>> ERROR: "__udivdi3" [drivers/net/wireless/ath/ath10k/ath10k_core.ko] undefined!
>> >>> ERROR: "__divdi3" [drivers/net/wireless/ath/ath10k/ath10k_core.ko] undefined!
>>
>> I'm not sure what this is about. The corresponding patch is here:
>>
>> https://patchwork.kernel.org/patch/10624567/
>>
>> I see some division in the patch but I can't immeaditely see what's
>> wrong. So is this a problem in the bot, in parisc architecture or with
>> the patch? Anyone have any good ideas? Arnd?
>>
>
> I think the problem is that 'clock_freq' is a 'u64', which means we can't use
> a normal 32-bit division. It looks like it cannot actually go beyond the
> range of a u32, so changing the type should be sufficient.
Great, thanks for the quick help :)
--
Kalle Valo
prev parent reply other threads:[~2018-10-12 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201810090804.eQbqAwdi%fengguang.wu@intel.com>
2018-10-12 14:32 ` [ath6kl:pending 10/15] ERROR: "__udivdi3" [drivers/net/wireless/ath/ath10k/ath10k_core.ko] undefined! Kalle Valo
2018-10-12 14:46 ` Arnd Bergmann
2018-10-12 14:49 ` Kalle Valo [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=878t3343um.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arnd@arndb.de \
--cc=ath10k@lists.infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pillair@codeaurora.org \
--cc=svishnoi@codeaurora.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