From: Frank Cusack <fcusack@fcusack.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.5.69 net/sunrpc/sunrpc_syms.c (trivial)
Date: Sat, 17 May 2003 20:45:28 -0700 [thread overview]
Message-ID: <20030517204528.A12071@google.com> (raw)
--- linux-2.5.69/net/sunrpc/sunrpc_syms.c.orig Sat May 17 20:44:29 2003
+++ linux-2.5.69/net/sunrpc/sunrpc_syms.c Sat May 17 20:44:37 2003
@@ -169,7 +169,7 @@
#ifdef RPC_DEBUG
rpc_unregister_sysctl();
#endif
-#ifdef CONFIG_PROCFS
+#ifdef CONFIG_PROC_FS
rpc_proc_exit();
#endif
}
reply other threads:[~2003-05-18 3:32 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=20030517204528.A12071@google.com \
--to=fcusack@fcusack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.