From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFCv2 0/7] Socket HAL part2
Date: Mon, 25 Nov 2013 13:22:50 +0200 [thread overview]
Message-ID: <1385378577-20503-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
These are fixes and some missing functionality for Socket HAL.
Andrei Emeltchenko (7):
android/socket: Check that create_record function exist
android/socket: Use default sec_level for listen
android/socket: Add error printing possible close() failure
android/socket: Use security level for connect
android/socket: Keep server iochannel reference
android/socket: Handle Android events for server socket
android/socket: Check create_rfsock returns valid structure
android/socket.c | 104 ++++++++++++++++++++++++++++++++++++++++++++++---------
1 file changed, 88 insertions(+), 16 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-11-25 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 11:22 Andrei Emeltchenko [this message]
2013-11-25 11:22 ` [RFCv2 1/7] android/socket: Check that create_record function exist Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 2/7] android/socket: Use default sec_level for listen Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 3/7] android/socket: Add error printing possible close() failure Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 4/7] android/socket: Use security level for connect Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 5/7] android/socket: Keep server iochannel reference Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 6/7] android/socket: Handle Android events for server socket Andrei Emeltchenko
2013-11-25 11:22 ` [RFCv2 7/7] android/socket: Check create_rfsock returns valid structure Andrei Emeltchenko
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=1385378577-20503-1-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.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;
as well as URLs for NNTP newsgroup(s).