From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] Fix memory leak when loading keys
Date: Tue, 24 Jan 2012 15:39:57 +0200 [thread overview]
Message-ID: <20120124133957.GA32584@x220> (raw)
In-Reply-To: <20120124133402.GA25057@samus>
Hi Vinicius,
On Tue, Jan 24, 2012, Vinicius Costa Gomes wrote:
> > In the future, could you please try to adopt the commit summary naming
> > convention we've started using where there's a short prefix to highlight
> > the part of the code the patch relates to. In this this case it should
> > have been "hciops: ...".
>
> Noted. Would you want me to resend my last series?
If you want to. Otherwise I'll fix it with "git commit --amend" myself.
Johan
next prev parent reply other threads:[~2012-01-24 13:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 23:13 [PATCH BlueZ v2 1/4] Add support for creating devices from the stored LTK's Vinicius Costa Gomes
2012-01-18 23:13 ` [PATCH BlueZ v2 2/4] Use the helper function to convert a string to a binary buffer Vinicius Costa Gomes
2012-01-18 23:13 ` [PATCH BlueZ v2 3/4] Fix memory leak when loading keys Vinicius Costa Gomes
2012-01-23 11:12 ` Johan Hedberg
2012-01-23 13:29 ` Vinicius Costa Gomes
2012-01-24 0:21 ` [PATCH BlueZ] " Vinicius Costa Gomes
2012-01-24 10:40 ` Anderson Lizardo
2012-01-24 10:46 ` Johan Hedberg
2012-01-24 11:46 ` Anderson Lizardo
2012-01-24 13:02 ` Johan Hedberg
2012-01-24 13:34 ` Vinicius Costa Gomes
2012-01-24 13:39 ` Johan Hedberg [this message]
2012-01-24 13:48 ` Vinicius Costa Gomes
2012-01-18 23:13 ` [PATCH BlueZ v2 4/4] Remove the SMP Long Term Key when the device is removed Vinicius Costa Gomes
2012-01-23 11:13 ` 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=20120124133957.GA32584@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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;
as well as URLs for NNTP newsgroup(s).