From: Marcel Holtmann <marcel@holtmann.org>
To: Victor Shcherbatyuk <Victor.Shcherbatyuk@tomtom.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] rfcomm/sock.c: rfcomm_sock_sendmsg() does not return error on a connection faulure
Date: Fri, 19 Dec 2008 08:00:42 +0100 [thread overview]
Message-ID: <1229670042.17082.29.camel@violet> (raw)
In-Reply-To: <C36B5BF556750D4282E3E0FA9ABEE628023B1019@nl-exc-01.intra.local>
Hi Victor,
> We noticed a problem, when a connection from the remote device is
> dropper the write() function does not return the error in the user
> space, returning 0 instead - indicating that 0 bytes are sent. We've
> also noticed that with some older kernels it used to work (2.6.13 vs
> 2.6.23-17). The patch fixes the problem.
that is a bug and your patch looks good. However can you use
git-format-patch and sent it again with proper Signed-off-by line for me
to apply.
Regards
Marcel
next prev parent reply other threads:[~2008-12-19 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 14:48 [PATCH] rfcomm/sock.c: rfcomm_sock_sendmsg() does not return error on a connection faulure Victor Shcherbatyuk
2008-12-19 7:00 ` Marcel Holtmann [this message]
2008-12-19 13:04 ` Victor Shcherbatyuk
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=1229670042.17082.29.camel@violet \
--to=marcel@holtmann.org \
--cc=Victor.Shcherbatyuk@tomtom.com \
--cc=linux-bluetooth@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