From: "John W. Linville" <linville@tuxdriver.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: marcel@holtmann.org, linux-wireless@vger.kernel.org,
linux-bluetooth@vger.kernel.org, davem@davemloft.net
Subject: Re: pull request: bluetooth-2.6 2010-10-18
Date: Mon, 18 Oct 2010 16:08:31 -0400 [thread overview]
Message-ID: <20101018200830.GA2443@tuxdriver.com> (raw)
In-Reply-To: <20101018055540.GA13511@vigoh>
On Mon, Oct 18, 2010 at 03:55:40AM -0200, Gustavo F. Padovan wrote:
> Hi John,
>
> Not sure if we still have time for a last minute fix, but here goes a
> fix for a NULL dereference in L2CAP layer for 2.6.36-rc8. Please also let
> me know if this is the right way to handle such last minute fix. Maybe you
> should want this directly through Dave.
>
> Thanks.
The fix seems fine to me. Given the short schedule, it might be best
to skip the middleman and have Dave pull directly from you?
Dave, be forewarned that Gustavo has based his tree off 2.6.36-rc8 --
dunno if you are ready to pull that into net-2.6 or not.
John
> Linux 2.6.36-rc8 (2010-10-14 16:26:43 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git master
>
> Nathan Holstein (1):
> Bluetooth: fix oops in l2cap_connect_req
>
> net/bluetooth/l2cap.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> --
> Gustavo F. Padovan
> ProFUSION embedded systems - http://profusion.mobi
>
--
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:[~2010-10-18 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 5:55 pull request: bluetooth-2.6 2010-10-18 Gustavo F. Padovan
2010-10-18 20:08 ` John W. Linville [this message]
2010-10-18 19:02 ` Gustavo F. Padovan
2010-10-21 7:54 ` 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=20101018200830.GA2443@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
/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).