netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: netdev@axxeo.de
Cc: netdev@vger.kernel.org, Ariel.Hendel@sun.com,
	greg.onufer@sun.com, jeff@garzik.org, Ashley.Saulsbury@sun.com,
	Matheos.Worku@sun.com
Subject: Re: [PATCH]: Third (final?) release of Sun Neptune driver
Date: Fri, 05 Oct 2007 14:18:09 -0700 (PDT)	[thread overview]
Message-ID: <20071005.141809.55498410.davem@davemloft.net> (raw)
In-Reply-To: <200710051846.19965.netdev@axxeo.de>

From: Ingo Oeser <netdev@axxeo.de>
Date: Fri, 5 Oct 2007 18:46:19 +0200

> Could this driver be split into more files. 8k lines per file
> is quite a lot. Although GCC might optimize it best this way :-)

Absolutely not!!!!!!!

I hate multiple file drivers, with a passion, they absolutely and
positivel suck.  I cringe every time I have to study a driver that
is broken up into multiple files.

They are a nightmare to hack on.  You have to keep typing in grep
commands, be a cscope wizard, or whatever to search around and find
the file in which the function or variable you want to learn about.

If it's all in one file, you can just sit in your single editor
buffer and get a lot of work done.

And to top it off such multi-file drivers tend to be a lot larger
and thus even harder to understand.

Multi-file drivers, just say no.

  parent reply	other threads:[~2007-10-05 21:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 10:12 [PATCH]: Third (final?) release of Sun Neptune driver David Miller
2007-10-05 15:35 ` Stephen Hemminger
2007-10-05 22:49   ` David Miller
2007-10-05 22:54   ` David Miller
2007-10-05 23:31     ` Jeff Garzik
2007-10-05 22:56   ` David Miller
2007-10-05 23:07   ` David Miller
2007-10-05 23:24   ` David Miller
2007-10-05 23:32     ` Jeff Garzik
2007-10-05 23:27   ` David Miller
2007-10-05 15:39 ` Stephen Hemminger
2007-10-05 21:12   ` David Miller
2007-10-05 21:18     ` Stephen Hemminger
2007-10-05 23:30       ` David Miller
2007-10-05 15:40 ` Stephen Hemminger
2007-10-05 21:12   ` David Miller
2007-10-05 21:14     ` Jeff Garzik
2007-10-05 21:21       ` Stephen Hemminger
2007-10-05 21:40         ` David Miller
2007-10-05 21:38       ` David Miller
2007-10-05 23:42   ` David Miller
2007-10-05 15:43 ` Stephen Hemminger
2007-10-06  0:04   ` David Miller
2007-10-06  0:28     ` Stephen Hemminger
2007-10-06  0:46       ` David Miller
2007-10-06  8:32       ` Johannes Berg
2007-10-05 16:46 ` Ingo Oeser
2007-10-05 16:49   ` Ingo Oeser
2007-10-06  0:08     ` David Miller
2007-10-08 16:04       ` Oliver Hartkopp
2007-10-05 16:55   ` Jeff Garzik
2007-10-05 17:45   ` Matheos Worku
2007-10-05 21:18   ` David Miller [this message]
2007-10-05 21:20   ` David Miller
     [not found]   ` <470677A0.5060502@sun.com>
2007-10-05 21:24     ` David Miller
2007-10-05 22:18   ` Matheos Worku
2007-10-05 22:43     ` David Miller
2007-10-06  0:10   ` David Miller
2007-10-08 16:01 ` Oliver Hartkopp
2007-10-08 23:08   ` David Miller

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=20071005.141809.55498410.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ariel.Hendel@sun.com \
    --cc=Ashley.Saulsbury@sun.com \
    --cc=Matheos.Worku@sun.com \
    --cc=greg.onufer@sun.com \
    --cc=jeff@garzik.org \
    --cc=netdev@axxeo.de \
    --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 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).