From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next-2.6 2011-02-17
Date: Mon, 21 Feb 2011 15:48:00 -0500 [thread overview]
Message-ID: <20110221204759.GL9650@tuxdriver.com> (raw)
In-Reply-To: <20110221201645.GC2965@joana>
On Mon, Feb 21, 2011 at 05:16:45PM -0300, Gustavo F. Padovan wrote:
> Hi John,
>
> * Gustavo F. Padovan <padovan@profusion.mobi> [2011-02-18 10:59:56 -0300]:
>
> > Hi John,
> >
> > Busy times at the Bluetooth subsystem. Here is another big set of patches
> > intended to 2.6.39. ;)
> >
> > One of the changes is the end of the L2CAP and SCO kernel modules. We just
> > merged them into the main bluetooth.ko module. It really never made sense to
> > have them separated.
> >
> > Then we have firmware support to a new Atheros device by Bala Shanmugam.
> > The First set of patches for Bluetooth Low Energy(LE) support, by Ville Tervo.
> > Low Energy is a new Bluetooth radio that will bring many new use cases to the
> > Bluetooth technology. Finally, LE connection update command support by Claudio
> > Takahasi. The rest is just bugs fixes and cleanups.
> >
> > Please pull, or let me know any doubts you have. Thanks.
>
> I saw you had a merge conflict between bluetooth-2.6 and bluetooth-next-2.6
> and I want to apologize for the extra work I caused to you. It was all my
> fault by not testing the merge of the my own trees. It won't happen again. ;)
Cool, thanks! It wasn't a big deal, but better if I can avoid it! :-)
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:[~2011-02-21 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 13:59 pull request: bluetooth-next-2.6 2011-02-17 Gustavo F. Padovan
2011-02-21 20:16 ` Gustavo F. Padovan
2011-02-21 20:48 ` 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=20110221204759.GL9650@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.