linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Balamurugan Mahalingam <mbalamurugan@atheros.com>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
	charubala@charubala.com
Subject: Re: [PATCH] Fix GUI crash while connecting Interlink Bluetooth Mouse in android platform.
Date: Tue, 19 Oct 2010 14:23:28 +0300	[thread overview]
Message-ID: <20101019112328.GA12554@jh-x301> (raw)
In-Reply-To: <1287482080-10093-1-git-send-email-mbalamurugan@atheros.com>

Hi,

On Tue, Oct 19, 2010, Balamurugan Mahalingam wrote:
> Crash is due to some junk characters in the device name.
> The device name is copied from a string variable after freeing the memory it points to, so there were some junk characters in it which was the reason for the crash.
> Fixing the issue by freeing the memory in string variable after device name is copied.
> 
> Signed-off-by: Balamurugan Mahalingam <mbalamurugan@atheros.com>
> ---
>  compat/sdp.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Looks like a good fix, but could you please fix your commit message and
resend:

1. The commit message doesn't so much describe the change as it does
some symptom in a downstream system (android). E.g. the summary line
should be something like "Fix accessing freed memory". You can still
talk about the background to this issue wrt. android but the main point
should be in a bluez-only context.

2. Keep the commit message lines below 74 characters so that it's
properly viewable on a 80-character wide terminal when running "git log"

3. Remove the signed-off-by line. We don't use that in userspace.

Johan

  reply	other threads:[~2010-10-19 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  9:54 [PATCH] Fix GUI crash while connecting Interlink Bluetooth Mouse in android platform Balamurugan Mahalingam
2010-10-19 11:23 ` Johan Hedberg [this message]
2010-10-19 12:01   ` Balamurugan Mahalingam

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=20101019112328.GA12554@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=charubala@charubala.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mbalamurugan@atheros.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).