Linux wireless drivers development
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	<linux-wireless@vger.kernel.org>
Subject: Re: [wireless-next:master 81/103] debugfs.c:undefined reference to `__udivdi3'
Date: Fri, 20 Jun 2014 10:04:38 +0300	[thread overview]
Message-ID: <2726638.LfDSnF5pNj@lx-wigig-72> (raw)
In-Reply-To: <53a34eca.II3U4c3qnUUeOSk1%fengguang.wu@intel.com>

On Friday, June 20, 2014 04:57:46 AM kbuild test robot wrote:
> tree:  
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git
> master head:   2e91606f5e1ec7329557dfc0e298c4c021acbb80
> commit: 7c0acf868d2e470c9d6a40091acf8d6444c01b57 [81/103] wil6210: Tx
> performance monitoring config: i386-randconfig-ha3-0620 (attached as
> .config)
> 
> All error/warnings:
> 
>    drivers/built-in.o: In function `wil_vring_debugfs_show':
> >> debugfs.c:(.text+0x39b9be): undefined reference to `__udivdi3'
> 
> ---
> 0-DAY kernel build testing backend              Open Source Technology
> Center http://lists.01.org/mailman/listinfo/kbuild                 Intel
> Corporation

Interesting finding. I use this code for long time and it was OK on both
32-bit and 64-bit platforms. I have different .config and compile
this driver as module. Anyway, bug is bug.
Sending patch in the separate mail.

Thanks, Vladimir

           reply	other threads:[~2014-06-20  7:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <53a34eca.II3U4c3qnUUeOSk1%fengguang.wu@intel.com>]

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=2726638.LfDSnF5pNj@lx-wigig-72 \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox