From: "John W. Linville" <linville@tuxdriver.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: bluetooth-2.6 2010-10-30
Date: Mon, 8 Nov 2010 15:57:05 -0500 [thread overview]
Message-ID: <20101108205704.GB2310@tuxdriver.com> (raw)
In-Reply-To: <20101030031503.GB24188@vigoh>
On Sat, Oct 30, 2010 at 04:15:03AM +0100, Gustavo F. Padovan wrote:
> Hi John,
>
> The following batch contains some bugfixes for 2.6.37. A fix for unaligned
> access in L2CAP, a Kconfig error, and two fixes related to security of
> the Bluetooth links. There is also a one line patch from Matthew Garret,
> that enables USB autosuspend for btusb module, which shall be completely
> safe. Please pull, thanks.
>
>
> The following changes since commit c1758012971e0410790b2bc96a77e26d7b286593:
>
> igb: Fix unused variable warning. (2010-10-27 19:43:55 -0700)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git master
Gustavo,
I'm happy to take your patches. But if you want me to pull from you
then I need your bluetooth-2.6 tree to be based upon wireless-2.6
(and bluetooth-next-2.6 to be based upon wireless-next-2.6), with only
the bluetooth patches on top.
If that is a problem, then you can send me a stack of patches for
me to apply manually instead. Otherwise I will get patches I don't
necessarily want pulled into wireless-2.6 and could even accidentally
push patches to davem that he might not want either.
Thanks,
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:[~2010-11-08 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 3:15 pull request: bluetooth-2.6 2010-10-30 Gustavo F. Padovan
2010-10-30 6:29 ` Luis R. Rodriguez
2010-11-08 20:57 ` John W. Linville [this message]
2010-11-08 21:15 ` 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=20101108205704.GB2310@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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).