From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: torvalds@linux-foundation.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, mcgrof@gmail.com,
Vikram Kandukuri <vkandukuri@atheros.com>,
Vikram Kandukuri <vikram.kandukuri@atheros.com>,
Alicke Xu <sxu@atheros.com>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] Bluetooth: Add DFU driver for Atheros Bluetooth chipset AR3011
Date: Wed, 20 Jan 2010 12:27:48 -0800 [thread overview]
Message-ID: <1264019268.5591.223.camel@localhost.localdomain> (raw)
In-Reply-To: <1264017679-19324-1-git-send-email-lrodriguez@atheros.com>
Hi Luis,
> Signed-off-by: Vikram Kandukuri <vikram.kandukuri@atheros.com>
> Signed-off-by: Alicke Xu <sxu@atheros.com>
> Reviewed-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>
> Linus, this was merged into linux-next already. The driver is small enough,
> it just uploads firmware, I figured it would likely be welcomed into 2.6.33-rc5.
> The patch is the same as it went into linux-next. The firmware is already
> merged as part of the linux-firmware git tree.
what is going on here? Overstepping myself and also Dave for merging a
new driver at this point of time in the development cycle.
The driver is small and self-contained, I agree on that. But remember
the reason why it was not part of 2.6.33-rc1. You guys actually screwed
up the submission. And I didn't get any fixes for 1.5 month. Now you are
pushing it like this?
Dave, I have no objection to merging this. So if you are happy in taking
in it this late, I include it in the round of fixes that I am putting
together.
Regards
Marcel
next prev parent reply other threads:[~2010-01-20 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:01 [PATCH] Bluetooth: Add DFU driver for Atheros Bluetooth chipset AR3011 Luis R. Rodriguez
2010-01-20 20:27 ` Marcel Holtmann [this message]
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
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=1264019268.5591.223.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=sxu@atheros.com \
--cc=torvalds@linux-foundation.org \
--cc=vikram.kandukuri@atheros.com \
--cc=vkandukuri@atheros.com \
/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