From: Johan Hedberg <johan.hedberg@gmail.com>
To: Santiago Carot-Nemesio <sancane@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Pull request git://gitorious.org/bluez-mcap-hdp/mcap-hdp.git for_upstream
Date: Thu, 18 Nov 2010 17:03:51 +0200 [thread overview]
Message-ID: <20101118150351.GA14348@jh-x301> (raw)
In-Reply-To: <1290092014-32574-1-git-send-email-sancane@gmail.com>
Hi,
On Thu, Nov 18, 2010, Santiago Carot-Nemesio wrote:
> Fix typos in adapter documentation (2010-11-16 13:39:43 +0000)
>
> are available in the git repository at:
> git://gitorious.org/bluez-mcap-hdp/mcap-hdp.git for_upstream
>
> José Antonio Santos Cadenas (9):
> Add reference counter to hdp_application
> Add reference counter to hdp_channel
> Notify a channel deleted when remote side has already deleted it
> Fix typos in mcap
> Set reference counter for mcls to gint
> Fix message error
> Remove magic number to check ECHO MDEPs in HDP
> Fixes to echo
> Check if the mcl insiede the device is correctly set before use it
>
> Santiago Carot-Nemesio (10):
> Add reference counter to hdp_device
> Remove MCL's before removing the application
> Add missed unrefs for hdp_tmp_dc_data
> Add reference counter to mcap_instances
> Add reference counter to mcap_mdl
> Remove old reference to mcap session in the name of variables
> Code refactorization in MCAP
> Fix dereference to NULL pointers during data channels creation
> Return proper response code if there is an error creating echo channel
> Check if MCAP Instance is already released when a callbacks comes back.
>
> health/hdp.c | 266 ++++++++++++++++++++++++++++++++----------------
> health/hdp_types.h | 4 +
> health/hdp_util.c | 55 ++++++++++-
> health/hdp_util.h | 8 ++
> health/mcap.c | 242 +++++++++++++++++++++++++------------------
> health/mcap_internal.h | 9 +-
> health/mcap_lib.h | 13 ++-
> health/mcap_sync.c | 22 ++--
> 8 files changed, 407 insertions(+), 212 deletions(-)
In general, please try to avoid such big sets of patches and send them
in smaller bits (as they get created) to linux-bluetooth. That makes
things easier for me and I am able to do a more thorough review.
However, I did a quick skim through of the patches and only found one
coding style issue (C++ style comment) which I fixed my self. So the
patches have now all been pushed upstream.
Johan
next prev parent reply other threads:[~2010-11-18 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:53 Pull request git://gitorious.org/bluez-mcap-hdp/mcap-hdp.git for_upstream Santiago Carot-Nemesio
2010-11-18 15:03 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-21 7:52 Jose Antonio Santos Cadenas
2010-10-22 13:43 ` Johan Hedberg
2010-10-14 10:57 Jose Antonio Santos Cadenas
2010-10-14 11:15 ` Johan Hedberg
2010-10-11 12:25 Jose Antonio Santos Cadenas
2010-10-11 21:31 ` Johan Hedberg
2010-10-11 22:25 ` Jose Antonio Santos Cadenas
2010-10-11 23:23 ` Jose Antonio Santos Cadenas
2010-10-12 9:35 ` Johan Hedberg
2010-10-12 9:57 ` Jose Antonio Santos Cadenas
2010-10-12 10:02 ` Jose Antonio Santos Cadenas
2010-10-12 10:10 ` Jose Antonio Santos Cadenas
2010-10-12 10:15 ` Johan Hedberg
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=20101118150351.GA14348@jh-x301 \
--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