From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH obexd 1/4] gobex: handle Single Response Mode (SRM) headers
Date: Wed, 11 Jan 2012 15:58:02 +0200 [thread overview]
Message-ID: <20120111135802.GC27506@x220> (raw)
In-Reply-To: <1325598744-18855-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Tue, Jan 03, 2012, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Single Response Mode (SRM) is a 1-byte quantity containing a value to
> enable or disable SRM, as well as to indicate support for SRM.
> ---
> gobex/gobex-transfer.c | 54 ++++++++++++--
> gobex/gobex.c | 194 +++++++++++++++++++++++++++++++++++++++++-------
> gobex/gobex.h | 1 +
> 3 files changed, 216 insertions(+), 33 deletions(-)
Since the rather long discussion with Hendrik doesn't seem to have
changed your mind about the correctness of these patches I've now
applied them upstream :)
Johan
prev parent reply other threads:[~2012-01-11 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 13:52 [PATCH obexd 1/4] gobex: handle Single Response Mode (SRM) headers Luiz Augusto von Dentz
2012-01-03 13:52 ` [PATCH obexd 2/4] gobex: handle Single Response Mode Parameters (SRMP) headers Luiz Augusto von Dentz
2012-01-03 13:52 ` [PATCH obexd 3/4] gobex: automatically use SRM when transport type is SOCK_SEQPACKET Luiz Augusto von Dentz
2012-01-03 15:58 ` Hendrik Sattler
2012-01-03 22:31 ` Luiz Augusto von Dentz
2012-01-04 18:48 ` Hendrik Sattler
2012-01-05 12:11 ` Luiz Augusto von Dentz
2012-01-05 22:40 ` Hendrik Sattler
2012-01-09 11:10 ` Luiz Augusto von Dentz
2012-01-03 13:52 ` [PATCH obexd 4/4] gobex: fix unit test when using SOCK_SEQPACKET Luiz Augusto von Dentz
2012-01-11 13:58 ` Johan Hedberg [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=20120111135802.GC27506@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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