From: Olaf Hering <olaf@aepfle.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: undefined references to __udivdi3 on powerpc
Date: Thu, 28 Feb 2008 17:44:08 +0100 [thread overview]
Message-ID: <20080228164408.GA8813@aepfle.de> (raw)
In-Reply-To: <39a171fd2cc7fec9813c5b3070b193ee@kernel.crashing.org>
On Thu, Feb 28, Segher Boessenkool wrote:
>> While debugging __divdi3 calls in drivers/crypto/hifn_795x.c (due to the
>> ndelay() delay call with a s64), I found even more breakage of that
>> sort. This is after a allnoconfig with ARCH=powerpc in 2.6.25-rc3,
>> plus CONFIG_MODULES=y and CONFIG_CRYPTO_DEV_HIFN_795X=y:
>
> I cannot reproduce this, but my tree has
>
> time: prevent the loop in timespec_add_ns() from being optimised away
>
> which is in -mm now. Could you try that patch?
Yes, this patch fixes it.
Thanks.
next prev parent reply other threads:[~2008-02-28 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 13:37 undefined references to __udivdi3 on powerpc Olaf Hering
2008-02-28 15:40 ` Segher Boessenkool
2008-02-28 16:44 ` Olaf Hering [this message]
2008-02-29 6:56 ` Adrian Bunk
2008-02-29 6:56 ` Adrian Bunk
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=20080228164408.GA8813@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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.