From: Greg KH <greg@kroah.com>
To: alan@redhat.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
luc@saillard.org, torvalds@osdl.org
Subject: Re: [PATCH] Restore PWC driver
Date: Mon, 7 Mar 2005 21:26:43 -0800 [thread overview]
Message-ID: <20050308052643.GA16222@kroah.com> (raw)
In-Reply-To: <200503072216.j27MGLqR024373@hera.kernel.org>
On Mon, Mar 07, 2005 at 09:49:40PM +0000, Linux Kernel Mailing List wrote:
> ChangeSet 1.1982.132.4, 2005/03/07 13:49:40-08:00, alan@lxorguk.ukuu.org.uk
>
> [PATCH] Restore PWC driver
>
> PWC has a new maintainer (Luc Saillard) and also the various contentious
> binary hooks removed and replaced with reverse engineering work.
>
> Please restore it to the kernel
Ick, Alan, couldn't you have had the decency to run this through the USB
developers, and at least pinged me on it? Especially due to all of the
hate-email I have gotten over this driver in the past.
As it is, the coding style sucks in places, and you didn't really need
to make it a new subdirectory (although due to the increased size of the
driver, it's probably better now...)
And, there's no MAINTAINERS entry for who I need to bug about this
thing.
Bleah.
So, who's going to fix up:
- the MAINTAINERS entry
- the coding style
- drop that unneeded changelog file
- fix the module help text to point to the proper file (or put
the file in the proper place.)
- get rid of the c++ crud in the header file
- drop the "magic" nonsense
- the ioctls to work on 64bit machines
?
And I found all of that in just a quick glance over the code...
Double bleah.
greg k-h
next parent reply other threads:[~2005-03-08 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503072216.j27MGLqR024373@hera.kernel.org>
2005-03-08 5:26 ` Greg KH [this message]
2005-03-08 5:32 ` [PATCH] Restore PWC driver Greg KH
2005-03-08 10:01 ` Alan Cox
2005-03-08 5:34 ` Christoph Hellwig
2005-03-08 10:01 ` Alan Cox
2005-03-08 11:11 ` Andrew Morton
2005-03-08 8:15 ` Luc Saillard
2005-03-08 10:03 ` Alan Cox
2005-03-08 9:59 ` Alan Cox
2005-03-08 14:13 ` Martin Hicks
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=20050308052643.GA16222@kroah.com \
--to=greg@kroah.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luc@saillard.org \
--cc=torvalds@osdl.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