mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Maurice Volaski <mvolaski@aecom.yu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: drbd-0.7.18 doesn't compile under 2.617-rc2 because SLAB_NO_REAP is missing
Date: Wed, 26 Apr 2006 14:06:43 -0700	[thread overview]
Message-ID: <20060426140643.d5775d55.rdunlap@xenotime.net> (raw)
In-Reply-To: <a0623092dc075772b201c@[129.98.90.227]>

On Wed, 26 Apr 2006 15:16:33 -0400 Maurice Volaski wrote:

> Being forwarded here from the drbd mailing list in case SLAB_NO_REAP 
> got removed from the kernel source inadvertently....

It's no longer used in the kernel tree.  Here's the patch
that removed it:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ac2b898ca6fb06196a26869c23b66afe7944e52e

> >
> >It was previously reported (twice) that drbd-0.7.17 didn't compile 
> >under the initial releases of 2.6.17. Neither does 0.7.18.
> >
> >/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd/drbd_main.c: In 
> >function `drbd_create_mempools':
> >/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd/drbd_main.c:1547: 
> >error: `SLAB_NO_REAP' undeclared (first use in this function)
> >/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd/drbd_main.c:1547: 
> >error: (Each undeclared identifier is reported only once
> >/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd/drbd_main.c:1547: 
> >error: for each function it appears in.)
> >make[3]: *** 
> >[/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd/drbd_main.o] 
> >Error 1
> >make[2]: *** 
> >[_module_/var/tmp/portage/drbd-0.7.18/work/drbd-0.7.18/drbd] Error 2
> >--

---
~Randy

      reply	other threads:[~2006-04-26 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 19:16 Maurice Volaski
2006-04-26 21:06 ` Randy.Dunlap [this message]

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=20060426140643.d5775d55.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvolaski@aecom.yu.edu \
    /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

all inboxes | Powered by JetHome®