From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: netdev@vger.kernel.org, linuxdev.baldrick@gmail.com, tom@herbertland.com
Subject: Re: [Patch net] kcm: fix a signedness in kcm_splice_read()
Date: Thu, 19 May 2016 11:27:12 -0700 (PDT) [thread overview]
Message-ID: <20160519.112712.1650104301380049541.davem@davemloft.net> (raw)
In-Reply-To: <1463519149-5998-1-git-send-email-xiyou.wangcong@gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Tue, 17 May 2016 14:05:49 -0700
> skb_splice_bits() returns int, kcm_splice_read() returns ssize_t,
> both are signed.
>
> We may need another patch to make them all ssize_t, but that
> deserves a separated patch.
>
> Fixes: 91687355b927 ("kcm: Splice support")
> Reported-by: David Binderman <linuxdev.baldrick@gmail.com>
> Cc: Tom Herbert <tom@herbertland.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Applied.
prev parent reply other threads:[~2016-05-19 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 21:05 [Patch net] kcm: fix a signedness in kcm_splice_read() Cong Wang
2016-05-19 18:27 ` David Miller [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=20160519.112712.1650104301380049541.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxdev.baldrick@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).