From: Peter Krystad <peter.krystad at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH 2/2] Remove unused variable, causes compile warning
Date: Wed, 31 Jul 2019 09:42:49 -0700 [thread overview]
Message-ID: <20190731164249.14383-2-peter.krystad@linux.intel.com> (raw)
In-Reply-To: 20190731164249.14383-1-peter.krystad@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
squashto: Add handling of incoming MP_JOIN requests
Signed-off-by: Peter Krystad <peter.krystad(a)linux.intel.com>
---
net/mptcp/token.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/mptcp/token.c b/net/mptcp/token.c
index 2324a477d513..d5ae77446590 100644
--- a/net/mptcp/token.c
+++ b/net/mptcp/token.c
@@ -77,7 +77,6 @@ static void new_req_token(struct request_sock *req,
static void new_req_join(struct request_sock *req, struct sock *sk,
const struct sk_buff *skb)
{
- const struct inet_request_sock *ireq = inet_rsk(req);
struct subflow_request_sock *subflow_req = subflow_rsk(req);
struct mptcp_sock *msk = mptcp_sk(sk);
u8 hmac[MPTCPOPT_HMAC_LEN];
--
2.17.2
next reply other threads:[~2019-07-31 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:42 Peter Krystad [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-01 16:04 [MPTCP] [PATCH 2/2] Remove unused variable, causes compile warning Mat Martineau
2019-08-07 17:12 Matthieu Baerts
2019-08-08 15:57 Matthieu Baerts
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=20190731164249.14383-2-peter.krystad@linux.intel.com \
--to=unknown@example.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.