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
Subject: Re: pull request: bluetooth-next-2.6 2010-10-13
Date: Fri, 15 Oct 2010 16:04:34 -0400 [thread overview]
Message-ID: <20101015200434.GB2438@tuxdriver.com> (raw)
In-Reply-To: <20101013034808.GA3205@vigoh>
On Wed, Oct 13, 2010 at 12:48:08AM -0300, Gustavo F. Padovan wrote:
> Hi John,
>
> Here goes the Bluetooth patches for the next merge window. In this
> patchset we have a new stream-oriented recvmsg() which is used in L2CAP
> and RFCOMM. Support for two new MacBookPro devices. A buffer overflow
> check for L2CAP to prevent frames exceeding the receiving MTU. All the
> rest are simple bugfixes. No big features this time.
>
> One notable change is in the MAINTAINERS file, From now and on I'm going
> to maintain the Bluetooth trees as well as send the pull requests to you.
> Despite this maintenance change, Marcel will remain helping with patch
> review, and ACK/NAK in the Bluetooth subsystem as he always did. Not a
> big change in the end. ;)
>
> Thanks,
>
> The following changes since commit 29b4433d991c88d86ca48a4c1cc33c671475be4b:
>
> net: percpu net_device refcount (2010-10-12 12:35:25 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-next-2.6.git master
Pulled, thanks -- I plan to send a pull request to Dave later today.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-10-15 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 3:48 pull request: bluetooth-next-2.6 2010-10-13 Gustavo F. Padovan
2010-10-13 21:41 ` Luis R. Rodriguez
2010-10-13 22:01 ` Gustavo F. Padovan
2010-10-15 20:04 ` John W. Linville [this message]
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=20101015200434.GB2438@tuxdriver.com \
--to=linville@tuxdriver.com \
--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).