From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/3] core: Fix trying to store NULL adapter->name
Date: Wed, 19 Dec 2012 09:32:57 +0200 [thread overview]
Message-ID: <20121219073257.GA4564@x220> (raw)
In-Reply-To: <1355879775-5809-1-git-send-email-anderson.lizardo@openbossa.org>
Hi Lizardo,
On Tue, Dec 18, 2012, Anderson Lizardo wrote:
> When BlueZ starts without a main.conf, adapter->name will be initially
> NULL, until adapter_name_changed() is called and name is set to "BlueZ".
>
> Before this, store_adapter_info() will try to access a NULL pointer.
>
> Fixes this GLib error:
>
> (bluetoothd:1721): GLib-CRITICAL **: g_key_file_set_string: assertion
> `string != NULL' failed
> ---
> src/adapter.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
All three patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2012-12-19 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 1:16 [PATCH BlueZ 1/3] core: Fix trying to store NULL adapter->name Anderson Lizardo
2012-12-19 1:16 ` [PATCH BlueZ 2/3] core: Remove bogus DBG() Anderson Lizardo
2012-12-19 1:16 ` [PATCH BlueZ 3/3] core: Remove reference to old "mgmtops" name Anderson Lizardo
2012-12-19 7:32 ` 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=20121219073257.GA4564@x220 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--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