Linux cryptographic layer development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: kbuild-all@01.org, herbert@gondor.apana.org.au,
	davem@davemloft.net, linux-crypto@vger.kernel.org,
	netdev@vger.kernel.org, dt@chelsio.com, atul.gupta@chelsio.com
Subject: [RFC PATCH] crypto/chelsio/chtls: chtls_sock_release() can be static
Date: Fri, 12 Apr 2019 12:57:40 +0800	[thread overview]
Message-ID: <20190412045740.GA5515@lkp-wsm-ep2> (raw)
In-Reply-To: <20190409152441.11256-1-atul.gupta@chelsio.com>


Fixes: c75f2018e89e ("crypto/chelsio/chtls: CPL for TLS client")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
 chtls_cm.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/crypto/chelsio/chtls/chtls_cm.c b/drivers/crypto/chelsio/chtls/chtls_cm.c
index 25a23e7..ba8316c 100644
--- a/drivers/crypto/chelsio/chtls/chtls_cm.c
+++ b/drivers/crypto/chelsio/chtls/chtls_cm.c
@@ -51,7 +51,7 @@ static unsigned char new_state[16] = {
 	/* TCP_CLOSING     */ TCP_CLOSING,
 };
 
-void chtls_sock_release(struct kref *ref)
+static void chtls_sock_release(struct kref *ref)
 {
 	struct chtls_sock *csk =
 		container_of(ref, struct chtls_sock, kref);
@@ -1339,7 +1339,7 @@ static void chtls_connect_req_arp_failure(void *handle, struct sk_buff *skb)
 	sock_put(sk);
 }
 
-void chtls_handshake_work(struct sock *sk)
+static void chtls_handshake_work(struct sock *sk)
 {
 	struct chtls_sock *csk = sk->sk_user_data;
 
@@ -1359,7 +1359,7 @@ void stop_hndsk_work(struct sock *sk)
 	}
 }
 
-void chtls_fix_pending_tx_buffers(struct sock *sk)
+static void chtls_fix_pending_tx_buffers(struct sock *sk)
 {
 	struct chtls_sock *csk = sk->sk_user_data;
 	struct tcp_sock *tp = tcp_sk(sk);

      parent reply	other threads:[~2019-04-12  4:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 15:24 [crypto 3/4] crypto/chelsio/chtls: CPL for TLS client Atul Gupta
2019-04-12  4:57 ` kbuild test robot
2019-04-12  4:57 ` kbuild test robot [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=20190412045740.GA5515@lkp-wsm-ep2 \
    --to=lkp@intel.com \
    --cc=atul.gupta@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=dt@chelsio.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@01.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox