Netdev List
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Small Bluetooth fix for 2.6.27-rc6
Date: Fri, 12 Sep 2008 05:56:44 +0200	[thread overview]
Message-ID: <1221191805.11498.14.camel@californication> (raw)

Hi Dave,

we discovered one tiny regression that was introduced with the default
link policy change in 2.6.27-rc1. This small patch fixes it and I hope
the commit message is detailed and clear enough to understand what went
wrong.

I also got pretty much annoyed by the following compiler warning:

  CC [M]  net/bluetooth/af_bluetooth.o
net/bluetooth/af_bluetooth.c:60: warning: ‘bt_key_strings’ defined but not used
net/bluetooth/af_bluetooth.c:71: warning: ‘bt_slock_key_strings’ defined but not used

So I finally fixed it (even if I didn't cause it), but I don't know
what's your take on fixing compiler warnings in -rc phase. It can
certainly wait for the next merge window.

Regards

Marcel


Please pull from

    git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master

This will update the following files:

 net/bluetooth/hci_core.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

through these ChangeSets:

Marcel Holtmann (1):
    [Bluetooth] Fix regression from using default link policy




             reply	other threads:[~2008-09-12  1:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12  3:56 Marcel Holtmann [this message]
2008-09-12  2:01 ` Small Bluetooth fix for 2.6.27-rc6 David Miller
2008-09-12  2:11   ` Marcel Holtmann
2008-09-12  2:12     ` David Miller
2008-09-12  2:15       ` Marcel Holtmann
2008-09-12  2:51         ` David Miller
2008-09-12  2:59           ` Marcel Holtmann
2008-09-12  3:03             ` David Miller

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=1221191805.11498.14.camel@californication \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@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