From: Marcel Holtmann <marcel@holtmann.org>
To: "Purdila, Octavian" <octavian.purdila@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: fix RFCOMM session reference counting issue
Date: Tue, 31 Jan 2012 07:09:38 -0800 [thread overview]
Message-ID: <1328022578.1955.215.camel@aeonflux> (raw)
In-Reply-To: <CAE1zotLDkVKnmDsOKbf6P9bxxLRsOcpvEtz6cm=_+avOYNZVbw@mail.gmail.com>
Hi Octavian,
> > I can follow your argumentation and seems reasonable to me.
> >
> > Have we run this against the BITE tester just to double check that not
> > by some stupid coincident it breaks qualification?
> >
> > Acked-by: Marcel Holtmann <marcel@holtmann.org>
> >
>
> Thanks for the review. I have ask around but we don't have a BITE
> tester available at our site. Is there any software tool we can use
> instead?
unfortunately there is nothing else when it comes to GAP, SDP and
RFCOMM.
Regards
Marcel
prev parent reply other threads:[~2012-01-31 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 15:10 [PATCH] Bluetooth: fix RFCOMM session reference counting issue Octavian Purdila
2012-01-30 22:05 ` Marcel Holtmann
2012-01-31 10:12 ` Purdila, Octavian
2012-01-31 10:21 ` Purdila, Octavian
2012-01-31 15:09 ` Marcel Holtmann [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=1328022578.1955.215.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=octavian.purdila@intel.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).