linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: ramm@ti.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/3] Bluetooth: Do not resolve name if entry was not found.
Date: Wed, 18 Jul 2012 15:39:56 +0300	[thread overview]
Message-ID: <20120718123956.GA2562@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1342613166-23651-1-git-send-email-ramm@ti.com>

Hi Ram,

On Wed, Jul 18, 2012, ramm@ti.com wrote:
> From: Ram Malovany <ramm@ti.com>
> 
> If entry wasn't found in the hci_inquiry_cache_lookup_resolve do not
> resolve the name.
> 
> Signed-off-by: Ram Malovany <ramm@ti.com>
> ---
>  net/bluetooth/hci_event.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)

I'm fine with all of these three patches but you might consider
improving the commit messages a bit. Especially with kernel patches it
doesn't hurt to have a bit more verbosity.

Also, formulating the summary line as "Fix ..." would be good since they
*are* all fixes (this can help fast-tracking them upstream). It's
particularly important for this first one to be clearly identifiable as
a fix since it's fixing a NULL pointer dereference (something that
should also have been mentioned in the commit message imo).

Another smaller cosmetic issue with the messages: usually the summary
lines do not end with a period.

Johan

  parent reply	other threads:[~2012-07-18 12:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 12:06 [PATCH 1/3] Bluetooth: Do not resolve name if entry was not found ramm
2012-07-18 12:06 ` [PATCH 2/3] Bluetooth: Do not resolve next name if the " ramm
2012-07-18 12:06 ` [PATCH 3/3] Bluetooth: Set name_state to unknown when entry name is empty ramm
2012-07-18 12:39 ` Johan Hedberg [this message]
2012-07-18 12:43   ` [PATCH 1/3] Bluetooth: Do not resolve name if entry was not found Malovany, Ram

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=20120718123956.GA2562@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ramm@ti.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).