From: Johan Hedberg <johan.hedberg@nokia.com>
To: Radoslaw Jablonski <ext-jablonski.radoslaw@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Add checking for agent reply state in adapter
Date: Tue, 28 Sep 2010 14:18:47 +0300 [thread overview]
Message-ID: <20100928111847.GA25553@jh-x301> (raw)
In-Reply-To: <1285665470-5261-1-git-send-email-ext-jablonski.radoslaw@nokia.com>
Hi Radek,
On Tue, Sep 28, 2010, Radoslaw Jablonski wrote:
> Added checking for agent reply state before cancelling agent in
> session_free(..). This check is needed to ensure that memory for
> agent request will be freed only once (In that case, free on this
> request is called later in the end of agent_reply func)
> ---
> src/adapter.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
Thanks. The patch has been pushed upstream with s/is_reply/got_reply/
which is more intuitive imho.
Johan
prev parent reply other threads:[~2010-09-28 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 9:17 [PATCH] Add checking for agent reply state in adapter Radoslaw Jablonski
2010-09-28 11:18 ` 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=20100928111847.GA25553@jh-x301 \
--to=johan.hedberg@nokia.com \
--cc=ext-jablonski.radoslaw@nokia.com \
--cc=linux-bluetooth@vger.kernel.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