linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gavin L Hemphill <hemphill@drea.dnd.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: problem with the latest linux-pmac-stable from linuxcare.com.au
Date: Mon, 29 Nov 1999 13:07:13 -0500	[thread overview]
Message-ID: <3842C0D1.38C1D2FD@drea.dnd.ca> (raw)


I just rsync'd the linux-pmac-stable tree this morning, and found that
it no longer builds.  There is a undefined reference to
"buffer_lowprio".  Now this function used to be defined in
"include/linux/fs.h"  but it appears to have been cleared out of there
(along with a bunch of other stuff refering to buffer). It appears to
still be used by "drivers/block/ll_rw_blk.c" and md.c and raid*.c.  Is
there any problem adding the functions back into fs.h, or is there a
better way to resolve the undefined references?
        G++

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~1999-11-29 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3842C0D1.38C1D2FD@drea.dnd.ca \
    --to=hemphill@drea.dnd.ca \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).