netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Jiri Benc <jbenc@suse.cz>, Christoph Hellwig <hch@infradead.org>,
	Joseph Jezak <josejx@gentoo.org>,
	mbuesch@freenet.de, linux-kernel@vger.kernel.org,
	NetDev <netdev@vger.kernel.org>
Subject: Re: Broadcom 43xx first results
Date: Tue, 06 Dec 2005 08:43:39 -0800	[thread overview]
Message-ID: <4395BFBB.8060304@candelatech.com> (raw)
In-Reply-To: <20051206150909.GB1999@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
> 
>>>That's because you still don't get how we do development.  The last thing
>>>we want is full-scale rewrites.  Submit patches to fix things based on
>>>whatever you want but do it incremental.
>>
>>We have got almost finished and working stack. Everything we need to do
>>is:
>>1. identify issues;
>>2. fix the issues; some of them will need broader discussion;
>>3. split it into several (potentially a lot of) reviewable patches;
>>4. clean up the drivers.
>>
>>I'm in phase 2 now (no interesting results yet). I don't think it is
> 
> 
> No, it does not work like that. You don't get nice, reviewable,
> mergeable patches by developing code independently for 3 years or so
> then attempting merge.
> 
> If devicescape code is better than mainline, merge it _now_. If it is
> not, drop it and start from mainline code.

Merge now even if it breaks the current tree?  I for one would certainly
rather he finish his work on it and get it more polished.  Reviewing and
testing something that actually works would be a lot more fun...


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2005-12-06 16:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Eiyw4-0003Ab-FW@www1.emo.freenet-rz.de>
2005-12-05 18:00 ` Broadcom 43xx first results Jiri Benc
2005-12-05 18:14   ` Michael Renzmann
2005-12-05 18:46     ` Jeff Garzik
2005-12-05 18:49       ` Jiri Benc
2005-12-05 18:54         ` Jeff Garzik
2005-12-05 19:11           ` Jiri Benc
2005-12-06  7:17       ` Michael Renzmann
     [not found]   ` <20051205190038.04b7b7c1-IhiK2ZEFs2oCVLCxKZUutA@public.gmane.org>
2005-12-05 18:38     ` Joseph Jezak
2005-12-05 18:55       ` Jiri Benc
2005-12-05 19:08         ` Jeff Garzik
2005-12-05 19:18           ` Jiri Benc
2005-12-05 19:53           ` Dave Jones
2005-12-05 20:09             ` Jeff Garzik
2005-12-06 15:10             ` Harald Welte
2005-12-06 19:05               ` Jeff Garzik
2005-12-07  7:16                 ` Harald Welte
2005-12-06 23:19               ` David S. Miller
2005-12-06 23:45                 ` Jeff Garzik
2005-12-07 13:34                 ` Michael Buesch
2005-12-08 11:32                   ` Jiri Benc
2005-12-08 12:07           ` Jiri Benc
2005-12-08 12:12             ` Arjan van de Ven
2005-12-08 13:03               ` Jiri Benc
2005-12-05 19:10         ` Christoph Hellwig
2005-12-05 19:31           ` Jiri Benc
2005-12-05 19:41             ` Christoph Hellwig
2005-12-05 20:11               ` Jiri Benc
2005-12-06 15:09                 ` Pavel Machek
2005-12-06 16:43                   ` Ben Greear [this message]
2005-12-06 23:25                     ` David S. Miller
2005-12-06 19:24                   ` Jeff Garzik
2005-12-06 15:04             ` Pavel Machek
2005-12-08  0:00             ` Michael Wu
2005-12-08  1:05               ` Jeff Garzik
2005-12-05 20:23     ` Michael Buesch
2005-12-05 20:42       ` Jiri Benc
2005-12-06  9:26         ` Kyle Moffett
2005-12-06 10:23           ` Luc Saillard
2005-12-06 22:47 Jean Tourrilhes
2005-12-07  7:11 ` Jouni Malinen
2005-12-07 19:16   ` Jean Tourrilhes
2005-12-07 19:47     ` Jouni Malinen
2005-12-07 19:05 ` Jean Tourrilhes

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=4395BFBB.8060304@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=hch@infradead.org \
    --cc=jbenc@suse.cz \
    --cc=josejx@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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).