From: Brian Gix <bgix@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Cc: padovan@profusion.mobi, rshaffer@codeaurora.org
Subject: Re: [PATCH 0/1] Add enc_read_blob_req() API to ATT
Date: Tue, 14 Dec 2010 11:54:17 -0800 [thread overview]
Message-ID: <4D07CB69.3000408@codeaurora.org> (raw)
In-Reply-To: <1292356246-24012-1-git-send-email-bgix@codeaurora.org>
Hi Gustavo, Vinicius,
On 12/14/2010 11:50 AM, Brian Gix wrote:
> Atomic change to add ATT_OP_READ_BLOB_REQ encoing to ATT. No dependancies.
>
>
This patch contains only the stand-alone ATT changes, and corrects the
ws issue identified by Vinicius.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
prev parent reply other threads:[~2010-12-14 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 19:50 [PATCH 0/1] Add enc_read_blob_req() API to ATT Brian Gix
2010-12-14 19:50 ` [PATCH] Added enc_read_blob_req() API to ATT transport, to enable the reading of attributes that exceed the length of the MTU Brian Gix
2010-12-14 20:29 ` Anderson Lizardo
2010-12-16 3:03 ` Anderson Lizardo
2010-12-14 19:54 ` Brian Gix [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=4D07CB69.3000408@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=rshaffer@codeaurora.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).