From: Jesse Sung <jesse.sung@canonical.com>
To: Petri Gynther <pgynther@google.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org
Cc: Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH] Bluetooth: btusb: Add BCM20702 firmware upgrade support
Date: Mon, 21 Apr 2014 18:32:10 +0800 [thread overview]
Message-ID: <5354F3AA.9070707@canonical.com> (raw)
Hi Marcel,
Sorry for creating a new thread instead since I didn't subscribe this
mailing list.
>>>> Interestingly, now that I look at that page more closely, Ubuntu 12.04
>>>> LTS with kernel 3.8 supports this already? Has Ubuntu made a patch
>>>> that bluetooth-next doesn't have?
>>>
>>> That is Ubuntu for you. They just push patches into their kernel and never give them back to upstream or make sure they get merged into bluetooth-next. I really dislike that behavior. It is always the easy way out instead of trying to do the right thing.
>>>
>>
>> See this page: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400
>
> It is a stupid userspace version that is racy as hell. Even the bug mentions that it should be done in the kernel. And I am pretty sure that was my initial comment as well. Just posting the userspace patch for reference.
No it's not the stupid userspace loader you're referring to.
And no, these patches are not pushed into Ubuntu kernel only.
These stupid patches were sent to this mailing list for review, for
three or four times, and all of them were rejected by you. The latest
version of patches that got rejected should be quite similar to Petri's.
Regards,
Jesse
next reply other threads:[~2014-04-21 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 10:32 Jesse Sung [this message]
2014-04-21 18:19 ` [PATCH] Bluetooth: btusb: Add BCM20702 firmware upgrade support Marcel Holtmann
2014-04-22 12:34 ` Jesse Sung
-- strict thread matches above, loose matches on Subject: below --
2014-04-09 1:05 Petri Gynther
2014-04-09 1:36 ` Marcel Holtmann
2014-04-09 2:41 ` Petri Gynther
2014-04-09 17:01 ` Marcel Holtmann
2014-04-09 20:06 ` Petri Gynther
2014-04-09 20:57 ` Marcel Holtmann
2014-05-06 2:53 ` Petri Gynther
2014-05-06 6:01 ` Marcel Holtmann
2014-05-07 22:28 ` Petri Gynther
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=5354F3AA.9070707@canonical.com \
--to=jesse.sung@canonical.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pgynther@google.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 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.