From: Wang Weidong <wangweidong1@huawei.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH net-next] dlm: use {lock|release}_sock instead, sctp_{lock|release}_sock
Date: Tue, 21 Jan 2014 16:33:23 +0800 [thread overview]
Message-ID: <52DE30D3.4070906@huawei.com> (raw)
As we remove the macros sctp_{lock|release}_sock in sctp.h, so change the use
in dlm as well.
This is a followup to ("sctp: remove macros sctp_{lock|release}_sock").
Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
---
fs/dlm/lowcomms.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index d90909e..ce53dff 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -713,11 +713,11 @@ static void process_sctp_notification(struct connection *con,
return;
/* Peel off a new sock */
- sctp_lock_sock(con->sock->sk);
+ lock_sock(con->sock->sk);
ret = sctp_do_peeloff(con->sock->sk,
sn->sn_assoc_change.sac_assoc_id,
&new_con->sock);
- sctp_release_sock(con->sock->sk);
+ release_sock(con->sock->sk);
if (ret < 0) {
log_print("Can't peel off a socket for "
"connection %d to node %d: err=%d",
--
1.7.12
WARNING: multiple messages have this Message-ID (diff)
From: Wang Weidong <wangweidong1@huawei.com>
To: David Miller <davem@davemloft.net>
Cc: <ccaulfie@redhat.com>, <teigland@redhat.com>,
<cluster-devel@redhat.com>, <netdev@vger.kernel.org>
Subject: [PATCH net-next] dlm: use {lock|release}_sock instead, sctp_{lock|release}_sock
Date: Tue, 21 Jan 2014 16:33:23 +0800 [thread overview]
Message-ID: <52DE30D3.4070906@huawei.com> (raw)
As we remove the macros sctp_{lock|release}_sock in sctp.h, so change the use
in dlm as well.
This is a followup to ("sctp: remove macros sctp_{lock|release}_sock").
Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
---
fs/dlm/lowcomms.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index d90909e..ce53dff 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -713,11 +713,11 @@ static void process_sctp_notification(struct connection *con,
return;
/* Peel off a new sock */
- sctp_lock_sock(con->sock->sk);
+ lock_sock(con->sock->sk);
ret = sctp_do_peeloff(con->sock->sk,
sn->sn_assoc_change.sac_assoc_id,
&new_con->sock);
- sctp_release_sock(con->sock->sk);
+ release_sock(con->sock->sk);
if (ret < 0) {
log_print("Can't peel off a socket for "
"connection %d to node %d: err=%d",
--
1.7.12
next reply other threads:[~2014-01-21 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 8:33 Wang Weidong [this message]
2014-01-21 8:33 ` [PATCH net-next] dlm: use {lock|release}_sock instead, sctp_{lock|release}_sock Wang Weidong
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=52DE30D3.4070906@huawei.com \
--to=wangweidong1@huawei.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 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.