From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-2.6 2011-06-08
Date: Thu, 9 Jun 2011 13:59:34 -0400 [thread overview]
Message-ID: <20110609175933.GA16802@tuxdriver.com> (raw)
In-Reply-To: <20110608194658.GD13036@joana>
On Wed, Jun 08, 2011 at 04:46:58PM -0300, Gustavo F. Padovan wrote:
> Hi John,
>
> First round of fixed for 3.0! There are here a regression fix for 1.1 and
> earlier devices and a fix in the shutdown of SCO sockets. Other 3 patches are
> warning shut up. And one byte leak to userspace fix.
>
> Please pull, thanks!
>
>
> The following changes since commit 51e65257142a87fe46a1ce5c35c86c5baf012614:
>
> iwlegacy: fix channel switch locking (2011-06-08 14:19:05 -0400)
>
> are available in the git repository at:
> master.kernel.org:/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git master
>
> David Miller (2):
...
> Bluetooth: Kill set but unused variable 'cmd' in cmtp_recv_capimsg()
Well, the patch submitter sounds familiar. :-) But killing an unused
variable isn't a bug fix. It doesn't do any damage, but I suspect that
Dave expects to be held to the same standards as everyone else.
Can you drop that one (and reapply it for 3.1)? Sorry for the trouble...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-06-09 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 19:46 pull request: bluetooth-2.6 2011-06-08 Gustavo F. Padovan
2011-06-09 17:59 ` John W. Linville [this message]
2011-06-09 18:34 ` Gustavo F. Padovan
2011-06-10 17:53 ` John W. Linville
2011-06-10 18:05 ` Gustavo F. Padovan
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=20110609175933.GA16802@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.