From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
devel@driverdev.osuosl.org,
Johan Hedberg <johan.hedberg@intel.com>,
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>,
jay.hung@mediatek.com
Subject: Re: [PATCH] Staging: btmtk_usb: Add hdev parameter to hdev->send driver callback
Date: Sat, 16 Nov 2013 08:39:50 +0900 [thread overview]
Message-ID: <20131115233950.GA17814@kroah.com> (raw)
In-Reply-To: <324E99F5-B9B7-4E56-BE91-42964AFF5BA8@holtmann.org>
On Sat, Nov 16, 2013 at 07:36:31AM +0900, Marcel Holtmann wrote:
> Hi Greg,
>
> >>>>> 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.
> >>
> >> Because it was sent to me by a developer?
> >
> > it is a problem when staging just becomes a dumping ground for drivers that the distributions find somewhere on the Internet or CD-ROMs. And then nobody has any intentions to clean up and integrate properly. This one did not even go through linux-bluetooth mailing list once. It was submitted right to staging. And then the submitter walked away.
>
> and if I quote the TODO file:
>
> TODO:
> - checkpatch.pl clean
> - determine if the driver should not be using a duplicate
> version of the usb-bluetooth interface code, but should
> be merged into the drivers/bluetooth/ directory and
> infrastructure instead.
> - review by the bluetooth developer community
>
> Please send any patches for this driver to Yu-Chen, Cho <acho@suse.com> and
> jay.hung@mediatek.com
>
> So from the submission we can assume that the submitter knew that this
> was duplicated code. The code also never got submitted for review to
> linux-bluetooth. And now 6 month later, none of the TODO items have
> been actually worked on.
>
> I do not know what your timeline is for removing drivers from staging,
> but this one seems to be a good candidate to get removed next.
6 months without any active contribution to getting it cleaned up and
merged is the timeline. Which this one fits, so yes, I will remove it
for 3.14, unless Jay or Cho is going to start doing work on this.
thanks,
greg k-h
prev parent reply other threads:[~2013-11-15 23:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 12:07 [PATCH] Staging: btmtk_usb: Add hdev parameter to hdev->send driver callback Geert Uytterhoeven
2013-11-15 12:30 ` Marcel Holtmann
2013-11-15 13:08 ` Dan Carpenter
2013-11-15 13:26 ` Marcel Holtmann
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 [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=20131115233950.GA17814@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acho@suse.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=jay.hung@mediatek.com \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).