From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Daniel Berlin <dberlin@redhat.com>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: u64 fun and PCI DMA not working for things behind bridges?
Date: Thu, 1 Mar 2001 21:18:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.10103012117070.21363-100000@callisto.of.borg> (raw)
In-Reply-To: <m2hf1dy1eo.fsf@dynamic-addr-83-177.resnet.rochester.edu>
On 1 Mar 2001, Daniel Berlin wrote:
> Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de> writes:
> > > I can't compile the drivers without optimization, or else i get
> > > references to functions that don't exist in the kernel, for some
> > > reason.
> >
> > What exact functions don't exist?
>
> Any extern inline functions.
`extern inline' is deprecated, in favor of `static inline'. During the last few
weeks, many of them were converted, albeit not in include/asm-ppc/.
I suppose this will solve the link problem with -O0 as well, since the compiler
will no longer think non-inlined functions are avilable externally?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-01 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 5:32 u64 fun and PCI DMA not working for things behind bridges? Daniel Berlin
2001-03-01 12:06 ` Michael Schmitz
2001-03-01 14:03 ` Benjamin Herrenschmidt
2001-03-01 14:05 ` Michael Schmitz
2001-03-01 15:06 ` Daniel Berlin
2001-03-01 20:18 ` Geert Uytterhoeven [this message]
2001-03-01 14:02 ` Benjamin Herrenschmidt
2001-03-01 15:08 ` Daniel Berlin
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=Pine.LNX.4.05.10103012117070.21363-100000@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=dberlin@redhat.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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;
as well as URLs for NNTP newsgroup(s).