netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "arun4linux" <arun4linux@indiatimes.com>
To: "Michael Richardson"<mcr@sandelman.ottawa.on.ca>,
	<netdev@oss.sgi.com>,
	"Linux Kernel Mailing List"<linux-kernel@vger.kernel.org>
Subject: Re: Re: pci-skeleton duplex check
Date: Sat, 14 Dec 2002 20:05:30 +0530	[thread overview]
Message-ID: <200212141428.TAA32351@WS0005.indiatimes.com> (raw)

&lt;&lt;Interfaces should NEVER change in patch level versions.
Just *DO NOT DO IT*.
&gt;&gt;I do agree on this.


This is a common complaint about linux kernel developers. And this always gives an insecure feeling  :-) for the device driver or kernel module programmers. 
This was one of the issues in my earlier company/work and they have gone for another OS.


Warm Regards


Arun
"Michael Richardson" wrote:



-----BEGIN PGP SIGNED MESSAGE-----


&gt;&gt;&gt;&gt;&gt; "Donald" == Donald Becker writes:
Donald&gt; The drivers in the kernel are now heavily modified and have significantly
Donald&gt; diverged from my version. Sure, you are fine with having someone else
Donald&gt; do the difficult and unrewarding debugging and maintainence work, while
Donald&gt; you work on just the latest cool hardware, change the interfaces and are
Donald&gt; concerned only with the current kernel version.

I agree strongly with Donald.

Interfaces should NEVER change in patch level versions.
Just *DO NOT DO IT*.

Go wild in odd-numbered.. get the interfaces right there.
But leave them alone afterward.

This is a fundamental tenant of being professional. Otherwise, the kernel
people are the biggest reason I've ever seen for using *BSD.
Microsoft is not the real enemy. Gratuitous change is.

] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [




Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com

 Buy the best in Movies at http://www.videos.indiatimes.com

Change the way you talk. Indiatimes presents Valufon, Your PC to Phone service with clear voice at rates far less than the normal ISD rates. Go to http://www.valufon.indiatimes.com. Choose your plan. BUY NOW.

             reply	other threads:[~2002-12-14 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 14:35 arun4linux [this message]
2002-12-14 16:14 ` Re: pci-skeleton duplex check Russell King
2002-12-14 21:26   ` Mr. James W. Laferriere
2002-12-15  0:37   ` Steffen Persvold
2002-12-16 18:55 ` Aravind Ceyardass
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14 14:35 arun4linux

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=200212141428.TAA32351@WS0005.indiatimes.com \
    --to=arun4linux@indiatimes.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcr@sandelman.ottawa.on.ca \
    --cc=netdev@oss.sgi.com \
    /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).