mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs-devel@linux.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.5: compile error in fs/filesystems.c
Date: Fri, 01 Mar 2002 08:48:30 +0100	[thread overview]
Message-ID: <87664giv8x.fsf@tigram.bogus.local> (raw)
In-Reply-To: <87vgchi2v8.fsf@tigram.bogus.local> <15486.50159.606621.827886@notabene.cse.unsw.edu.au> <87bse9hzok.fsf@tigram.bogus.local> <15486.54383.958359.357643@notabene.cse.unsw.edu.au>
In-Reply-To: <15486.54383.958359.357643@notabene.cse.unsw.edu.au> (Neil Brown's message of "Fri, 1 Mar 2002 12:07:59 +1100 (EST)")

Hi Neil,

Neil Brown <neilb@cse.unsw.edu.au> writes:

> There have been a number of problem reports on linux-kernel over the
> last year or two from people who cannot load nfsd.o as a module.
> Often it is because they originally compiled without and NFSD support
> at all, but subsequently decided that wanted to compile and load
> nfsd.o
>
> This works for many modules (e.g. filesystems)  It is reasonable that
> it work for nfsd as well.
>
> I thought that the cost of always including the hooks to load nfsd was
> minimal, and worth the consistency/convenience.
>
> Does that seem reasonable to you?

Ok, I didn't think of that. Thanks for clarifying.

Regards, Olaf.

      reply	other threads:[~2002-03-01  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 23:49 Olaf Dietsche
2002-02-28 23:57 ` Neil Brown
2002-03-01  0:58   ` Olaf Dietsche
2002-03-01  1:07     ` Neil Brown
2002-03-01  7:48       ` Olaf Dietsche [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=87664giv8x.fsf@tigram.bogus.local \
    --to=olaf.dietsche--list.linux-kernel@exmail.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs-devel@linux.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®