From: Jeff Layton <jlayton@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, nfsv4@linux-nfs.org
Subject: [PATCH 3/7] SUNRPC: export svc_sock_update_bufs
Date: Tue, 18 Dec 2007 15:19:38 -0500 [thread overview]
Message-ID: <1198009182-27895-4-git-send-email-jlayton@redhat.com> (raw)
In-Reply-To: <1198009182-27895-3-git-send-email-jlayton@redhat.com>
Needed since the plan is to not have a svc_create_thread helper and to
have current users of that function just call kthread_run directly.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
---
net/sunrpc/sunrpc_syms.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/net/sunrpc/sunrpc_syms.c b/net/sunrpc/sunrpc_syms.c
index 27bb185..618e84b 100644
--- a/net/sunrpc/sunrpc_syms.c
+++ b/net/sunrpc/sunrpc_syms.c
@@ -79,6 +79,7 @@ EXPORT_SYMBOL(svc_auth_register);
EXPORT_SYMBOL(auth_domain_lookup);
EXPORT_SYMBOL(svc_authenticate);
EXPORT_SYMBOL(svc_set_client);
+EXPORT_SYMBOL(svc_sock_update_bufs);
/* RPC statistics */
#ifdef CONFIG_PROC_FS
--
1.5.3.3
next prev parent reply other threads:[~2007-12-18 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 20:19 [PATCH 0/7] Intro: convert lockd to kthread and fix use-after-free (try #3) Jeff Layton
2007-12-18 20:19 ` [PATCH 1/7] SUNRPC: Allow svc_pool_map_set_cpumask to work with any task Jeff Layton
2007-12-18 20:19 ` [PATCH 2/7] SUNRPC: spin svc_rqst initialization to its own function Jeff Layton
2007-12-18 20:19 ` Jeff Layton [this message]
2007-12-18 20:19 ` [PATCH 4/7] NLM: Initialize completion variable in lockd_up Jeff Layton
2007-12-18 20:19 ` [PATCH 5/7] NLM: Have lockd call try_to_freeze Jeff Layton
2007-12-18 20:19 ` [PATCH 6/7] NLM: Convert lockd to use kthreads Jeff Layton
2007-12-18 20:19 ` [PATCH 7/7] NLM: Add reference counting to lockd Jeff Layton
2007-12-19 19:15 ` [PATCH 0/7] Intro: convert lockd to kthread and fix use-after-free (try #3) Tomasz Kłoczko
2008-01-05 16:44 ` J. Bruce Fields
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=1198009182-27895-4-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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®