From: Mike Shuey <shuey@purdue.edu>
To: oleg.drokin@intel.com
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
HPDD-discuss@ml01.01.org, Mike Shuey <shuey@purdue.edu>
Subject: [PATCH v3 3/8] staging: lustre: lnet: dead code - remove LNetSetAsync
Date: Tue, 19 May 2015 10:14:34 -0400 [thread overview]
Message-ID: <1432044879-28923-4-git-send-email-shuey@purdue.edu> (raw)
In-Reply-To: <1432044879-28923-1-git-send-email-shuey@purdue.edu>
LNetSetAsync() returns 0, and is never called. Doesn't exist in the Intel
tree, either. Remove it.
Signed-off-by: Mike Shuey <shuey@purdue.edu>
---
drivers/staging/lustre/include/linux/lnet/api.h | 1 -
drivers/staging/lustre/lnet/lnet/lib-move.c | 24 -----------------------
2 files changed, 0 insertions(+), 25 deletions(-)
diff --git a/drivers/staging/lustre/include/linux/lnet/api.h b/drivers/staging/lustre/include/linux/lnet/api.h
index cd86517..c4dc1b2 100644
--- a/drivers/staging/lustre/include/linux/lnet/api.h
+++ b/drivers/staging/lustre/include/linux/lnet/api.h
@@ -209,7 +209,6 @@ int LNetGet(lnet_nid_t self,
int LNetSetLazyPortal(int portal);
int LNetClearLazyPortal(int portal);
int LNetCtl(unsigned int cmd, void *arg);
-int LNetSetAsync(lnet_process_id_t id, int nasync);
/** @} lnet_misc */
diff --git a/drivers/staging/lustre/lnet/lnet/lib-move.c b/drivers/staging/lustre/lnet/lnet/lib-move.c
index ba59fe7..433faae 100644
--- a/drivers/staging/lustre/lnet/lnet/lib-move.c
+++ b/drivers/staging/lustre/lnet/lnet/lib-move.c
@@ -2434,27 +2434,3 @@ LNetDist(lnet_nid_t dstnid, lnet_nid_t *srcnidp, __u32 *orderp)
return -EHOSTUNREACH;
}
EXPORT_SYMBOL(LNetDist);
-
-/**
- * Set the number of asynchronous messages expected from a target process.
- *
- * This function is only meaningful for userspace callers. It's a no-op when
- * called from kernel.
- *
- * Asynchronous messages are those that can come from a target when the
- * userspace process is not waiting for IO to complete; e.g., AST callbacks
- * from Lustre servers. Specifying the expected number of such messages
- * allows them to be eagerly received when user process is not running in
- * LNet; otherwise network errors may occur.
- *
- * \param id Process ID of the target process.
- * \param nasync Number of asynchronous messages expected from the target.
- *
- * \return 0 on success, and an error code otherwise.
- */
-int
-LNetSetAsync(lnet_process_id_t id, int nasync)
-{
- return 0;
-}
-EXPORT_SYMBOL(LNetSetAsync);
--
1.7.1
next prev parent reply other threads:[~2015-05-19 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:14 [PATCH v3 0/8] staging: lustre: lnet: code cleanups Mike Shuey
2015-05-19 14:14 ` [PATCH v3 1/8] staging: lustre: lnet: lnet: code cleanups - variable declarations Mike Shuey
2015-05-19 14:14 ` [PATCH v3 2/8] staging: lustre: lnet: dead code - remove lnet_fini_locks Mike Shuey
2015-05-19 14:14 ` Mike Shuey [this message]
2015-05-19 14:14 ` [PATCH v3 4/8] staging: lustre: lnet: lnet: Module is LNet, not Portals Mike Shuey
2015-05-19 14:14 ` [PATCH v3 5/8] staging: lustre: lnet: o2iblnd: code cleanup - align whitespace Mike Shuey
2015-05-19 14:14 ` [PATCH v3 6/8] staging: lustre: lnet: socklnd: code cleanup - align spacing Mike Shuey
2015-05-19 14:14 ` [PATCH v3 7/8] staging: lustre: lnet: selftest: code cleanup - variable spacing, indentation Mike Shuey
2015-05-19 14:14 ` [PATCH v3 8/8] staging: lustre: lnet: remove LNET_MUTEX_LOCK macro Mike Shuey
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=1432044879-28923-4-git-send-email-shuey@purdue.edu \
--to=shuey@purdue.edu \
--cc=HPDD-discuss@ml01.01.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
/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®