All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Jes Sorensen <jes@trained-monkey.org>,
	netdev@vger.kernel.org, jaswinder@infradead.org
Subject: Re: [PATCH] firmware: convert acenic driver to request_firmware()
Date: Wed, 18 Jun 2008 12:26:07 -0400	[thread overview]
Message-ID: <4859371F.8090404@garzik.org> (raw)
In-Reply-To: <1213805681.26255.1312.camel@pmac.infradead.org>

David Woodhouse wrote:
> I believe you didn't respond to this, but just spouted the same
> complaint at another patch which was posted for review, without even
> seeming to have _looked_ at the part of that patch which really needed
> reviewing.
> 
> This has needed doing for a long time, and I've finally got off my
> posterior and started working on it. If you wanted it done precisely
> your way, you could always have done it yourself. As it is, we have a
> minor disagreement about some of the details, but it still needs doing.
> And since it still seems to be me doing it and not you, I'm still doing
> it the way I believe is best.


So, if you get an unhappy review, the reviewer must do your work for 
you?  That doesn't work for university students, and that doesn't fly here.

We are in the part of the Linux kernel coding process called 'taking 
feedback'.

The onus is on YOU to make your work friendly to both users and developers.

You can do whatever you please, but if its not friendly to Linux users 
(our customers) or Linux developers, it's mostly dead in the water. 
Those are my concerns, which you repeatedly fail to address.

For Pete's sake, you haven't even been able to admit the obvious:  these 
patches have a major, major chance of producing a non-working driver for 
users.

Your patch and your goal mean nothing if Linux users wind up having to 
jump through a dozen new hoops, just to ensure that a driver working 
yesterday continues to work today.  That's just plain bad engineering, 
no matter how noble the goal.

	Jeff



  reply	other threads:[~2008-06-18 16:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  9:25 [PATCH] firmware: convert acenic driver to request_firmware() David Woodhouse
2008-06-16 16:25 ` Jes Sorensen
2008-06-16 17:23   ` David Woodhouse
2008-06-17 16:50     ` Jes Sorensen
2008-06-17 16:52       ` David Woodhouse
2008-06-18 16:29       ` David Woodhouse
2008-06-16 20:34 ` Jeff Garzik
2008-06-16 21:45   ` David Woodhouse
2008-06-16 22:11     ` Jeff Garzik
2008-06-17 10:40       ` David Woodhouse
2008-06-18 16:14         ` David Woodhouse
2008-06-18 16:26           ` Jeff Garzik [this message]
2008-06-18 16:43             ` David Woodhouse
2008-06-18 16:45               ` David Woodhouse
2008-06-18 16:52                 ` Jes Sorensen

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=4859371F.8090404@garzik.org \
    --to=jeff@garzik.org \
    --cc=dwmw2@infradead.org \
    --cc=jaswinder@infradead.org \
    --cc=jes@trained-monkey.org \
    --cc=netdev@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 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.