From: Johan Hedberg <johan.hedberg@gmail.com>
To: Santiago Carot-Nemesio <sancane@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/4] attrib-server: Move GAP attributes inside gatt_server struct
Date: Mon, 9 Jan 2012 14:29:11 +0200 [thread overview]
Message-ID: <20120109122911.GA1481@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1325245509-14359-1-git-send-email-sancane@gmail.com>
Hi Santiago,
On Fri, Dec 30, 2011, Santiago Carot-Nemesio wrote:
> ---
> src/attrib-server.c | 30 ++++++++++++++++++------------
> 1 files changed, 18 insertions(+), 12 deletions(-)
All four patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2012-01-09 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 11:45 [PATCH 1/4] attrib-server: Move GAP attributes inside gatt_server struct Santiago Carot-Nemesio
2011-12-30 11:45 ` [PATCH 2/4] gatt-service: Delete attributes when service registration fails Santiago Carot-Nemesio
2011-12-30 11:45 ` [PATCH 3/4] gatt-service: Add missing user_data parameter for callbacks Santiago Carot-Nemesio
2011-12-30 11:45 ` [PATCH 4/4] gatt-example: Fix memory leak Santiago Carot-Nemesio
2012-01-09 12:29 ` 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=20120109122911.GA1481@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sancane@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;
as well as URLs for NNTP newsgroup(s).