mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cantab.net>
To: John Covici <covici@ccs.covici.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.8 nbd.c doesn't compile
Date: Wed, 17 Apr 2002 21:05:21 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20020417210154.00adde30@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <m33cxuw23g.fsf@ccs.covici.com>

Compilation is already fixed in the current bitkeeper tree 
(linux.bkbits.net/linux-2.5). so you can either get that or you can apply 
the patch I posted this morning fixing this problem.

You can find the patch in the archives:

http://marc.theaimsgroup.com/?l=linux-kernel&m=101897350106638&w=2

Note patch compiles but is otherwise untested.

Best regards,

Anton

At 20:34 17/04/02, John Covici wrote:
>When I try to compile 2.5.8 with nbd as a module, I get lots of error
>saying structure has no member queue_lock .
>
>Any assistance would be appreciated.
>
>--
>          John Covici
>          covici@ccs.covici.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

-- 
   "I've not lost my mind. It's backed up on tape somewhere." - Unknown
-- 
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


  reply	other threads:[~2002-04-17 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 19:34 John Covici
2002-04-17 20:05 ` Anton Altaparmakov [this message]
2002-04-17 21:24   ` John Covici

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=5.1.0.14.2.20020417210154.00adde30@pop.cus.cam.ac.uk \
    --to=aia21@cantab.net \
    --cc=covici@ccs.covici.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®