linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hendricks <khendricks@ivey.uwo.ca>
To: linuxppc-dev@lists.linuxppc.org, Paul Mackerras <paulus@linuxcare.com>
Subject: Error compiling Paul's latest stable kernel : missing buffer_lowprio in include/linux/fs.h
Date: Wed, 17 Nov 1999 22:43:17 -0500	[thread overview]
Message-ID: <99111722474100.07507@localhost.localdomain> (raw)


Hi,

I seem to be getting the following error when building Paul's latest stable
kernel rsynced just this morning from Paul's linuxcare.com.au site.

The error message I get is that buffer_lowprio is undefined.  Unfortunately it
is used in drivers/block/md.c, raid5.c, and ll_rw_blk.c).  I looked in my old
2.2.13 kernel source tree and it was previously defined in include/linux/fs.h
but in the latest stable kernel its definitiion has been removed.

Any ideas here would be greatly appreciated.

Thanks,

Kevin

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

                 reply	other threads:[~1999-11-18  3:43 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=99111722474100.07507@localhost.localdomain \
    --to=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.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;
as well as URLs for NNTP newsgroup(s).