From: David Miller <davem@davemloft.net>
To: error27@gmail.com
Cc: baum@tehutinetworks.net, andy@greyhouse.net, jpirko@redhat.com,
shemminger@vyatta.com, eric.dumazet@gmail.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] tehuti: return -EFAULT on copy_to_user errors
Date: Thu, 03 Jun 2010 03:29:22 -0700 (PDT) [thread overview]
Message-ID: <20100603.032922.93373171.davem@davemloft.net> (raw)
In-Reply-To: <20100603100535.GT5483@bicker>
From: Dan Carpenter <error27@gmail.com>
Date: Thu, 3 Jun 2010 12:05:35 +0200
> copy_to_user() returns the number of bytes remaining but we want to
> return a negative error code here.
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Applied.
prev parent reply other threads:[~2010-06-03 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 10:05 [patch] tehuti: return -EFAULT on copy_to_user errors Dan Carpenter
2010-06-03 10:29 ` 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=20100603.032922.93373171.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=baum@tehutinetworks.net \
--cc=eric.dumazet@gmail.com \
--cc=error27@gmail.com \
--cc=jpirko@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).