[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181206075837.13336-1-jakub.audykowicz@gmail.com>
Date: Thu, 6 Dec 2018 08:58:37 +0100
From: Jakub Audykowicz <jakub.audykowicz@...il.com>
To: linux-sctp@...r.kernel.org, vyasevich@...il.com,
nhorman@...driver.com, marcelo.leitner@...il.com,
davem@...emloft.net
Cc: netdev@...r.kernel.org,
Jakub Audykowicz <jakub.audykowicz@...il.com>
Subject: [PATCH net] sctp: fix pr_warn max_data argument type mismatch
My previous patch introduced a compilation warning regarding a type
mismatch (int vs size_t). This is a one-letter fix for good housekeeping.
Signed-off-by: Jakub Audykowicz <jakub.audykowicz@...il.com>
---
net/sctp/chunk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/sctp/chunk.c b/net/sctp/chunk.c
index d5b91bc8a377..ee5638358ad5 100644
--- a/net/sctp/chunk.c
+++ b/net/sctp/chunk.c
@@ -194,7 +194,7 @@ struct sctp_datamsg *sctp_datamsg_from_user(struct sctp_association *asoc,
if (unlikely(!max_data)) {
max_data = sctp_min_frag_point(sctp_sk(asoc->base.sk),
sctp_datachk_len(&asoc->stream));
- pr_warn_ratelimited("%s: asoc:%p frag_point is zero, forcing max_data to default minimum (%d)",
+ pr_warn_ratelimited("%s: asoc:%p frag_point is zero, forcing max_data to default minimum (%ld)",
__func__, asoc, max_data);
}
--
2.17.1
Powered by blists - more mailing lists