From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vikram Kandukuri <Vikram.Kandukuri@atheros.com>,
SongXing Xu <SongXing.Xu@atheros.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] Bluetooth: Add DFU driver for Atheros Bluetooth chipset AR3011
Date: Wed, 20 Jan 2010 15:01:17 -0800 [thread overview]
Message-ID: <43e72e891001201501n2088a40fn7d6ca2bef50c7c10@mail.gmail.com> (raw)
In-Reply-To: <1264027973.5591.241.camel@localhost.localdomain>
On Wed, Jan 20, 2010 at 2:52 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> As I said, if Dave is willing to take it, then I cherry-pick it for you
> and include it with my next round of fixes.
Well it enables hardware, so yes, I think it'd be good to add to
2.6.33-rc5, despite its historical issues on route upstream. Otherwise
I have to poke distributions to carry the driver externally anyway,
and I don't see the point in that if we still have a few RC cycles
left and this driver is really small.
Dave, please let me know if including this driver is unacceptable. I
honestly fail to understand the reasons for it to not go into
2.6.33-rcX.
Luis
prev parent reply other threads:[~2010-01-20 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:01 Luis R. Rodriguez
2010-01-20 20:27 ` Marcel Holtmann
2010-01-20 21:08 ` Luis R. Rodriguez
2010-01-20 22:52 ` Marcel Holtmann
2010-01-20 22:56 ` David Miller
2010-01-20 23:01 ` Luis R. Rodriguez [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=43e72e891001201501n2088a40fn7d6ca2bef50c7c10@mail.gmail.com \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=SongXing.Xu@atheros.com \
--cc=Vikram.Kandukuri@atheros.com \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®