From: Marcel Holtmann <marcel@holtmann.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
devel@driverdev.osuosl.org,
Johan Hedberg <johan.hedberg@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yu-Chen Cho <acho@suse.com>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org development"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Staging: btmtk_usb: Add hdev parameter to hdev->send driver callback
Date: Fri, 15 Nov 2013 22:26:41 +0900 [thread overview]
Message-ID: <F615BA13-BEC1-457B-8002-BC6C149039EA@holtmann.org> (raw)
In-Reply-To: <20131115130820.GS5302@mwanda>
Hi Dan,
>> while this is patch is correct, I do not really care about staging drivers that actually bluntly violate my copyright.
>>
>
> That's very cryptic.
>
> What is going on here? I googled it and I wasn't able to find what you
> are talking about. Care to give us a hint and what you want us to do
> here?
the last time I checked, the majority of drivers/bluetooth/btusb.c has been written by myself. Now go and compare btusb.c to btmtk_usb.[ch].
> I have also added Johan Hedberg to the CC list because he also helped
> break the build. Don't do that.
Yes, we are doing exactly that. It is a staging driver. I could not care less if a staging drivers breaks the build or not.
If anybody cares about this driver, then take the time to merge it upstream. It has never been submitted to linux-bluetooth mailing list.
There are drivers that should have never been merged into staging. This is one of them. Look for yourself and explain to me why this driver is part of staging in the first place.
Regards
Marcel
next prev parent reply other threads:[~2013-11-15 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 12:07 Geert Uytterhoeven
2013-11-15 12:30 ` Marcel Holtmann
2013-11-15 13:08 ` Dan Carpenter
2013-11-15 13:26 ` Marcel Holtmann [this message]
2013-11-15 21:29 ` Greg Kroah-Hartman
2013-11-15 22:26 ` Marcel Holtmann
2013-11-15 22:36 ` Marcel Holtmann
2013-11-15 23:39 ` Greg Kroah-Hartman
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=F615BA13-BEC1-457B-8002-BC6C149039EA@holtmann.org \
--to=marcel@holtmann.org \
--cc=acho@suse.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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 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®