All of lore.kernel.org
 help / color / mirror / Atom feed
From: William D Waddington <william.waddington@beezmo.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, Al Boldi <a1426z@gawab.com>
Subject: Re: Please release a stable kernel Linux 3.0
Date: Thu, 28 Jun 2007 08:28:48 -0700	[thread overview]
Message-ID: <4683D3B0.1040708@beezmo.com> (raw)
In-Reply-To: <4683983E.5020103@aitel.hist.no>



Helge Hafting wrote:
> Bill Waddington wrote:
>> (And taking my drivers main-line isn't an option.  It would be fine
>> with me, but there is *zero* chance that my funky code would be
>> welcomed into the tree.)
>>   
> If the only merge-stopper is code quality, why not
> post your driver and get some feedback?  Cleaning up code
> will take some effort of course;
> but once it is done, you're protected from module API changes. . .

Fair enough:
http://www.tahomatech.com/downloads/drivers/linux_2.6/pci/x86/compressed_tarfiles/
or for your browsing pleasure:
http://www.tahomatech.com/downloads/drivers/linux_2.6/pci/x86/files/

But I really don't see much hope :(  Coding style, masses of ioctls,
build and install technique,  limited user base, etc, etc, etc...  Most
of the above to keep API compatibility with other OS/older drivers -
back to SunOS 4.1.3.  (BTW, it does seem to work...)

And I probably have the license wrong.  The code has always been in
the public domain.  (Advice welcome...)

It really isn't that important to me to get this into the mainline,
or to have a stable kernel API.  I _might_ argue that a stable and
well documented kernel API (DKI) is a sign of a grown-up OS, but I
won't :)  It isn't that hard to recode for API changes.  There's always
LDD17 or 18 or 99 or whatever...

My (mild) beef is more like what I take to be Al's point: it feels like
there is a kind of hostility toward out-of-tree maintainers.  Why not
encourage _all_ of us who are beavering away at open-source code?  My
stuff doesn't belong in mainline, but it _is_ open, and in some minor
way allows more folks to run Linux.

A cleaned-up, consistent, and out-of-tree friendly way of handling API
changes might help us all.

Thanks for listening,
Bill

-- 
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
william.waddington@beezmo.com
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch

  reply	other threads:[~2007-06-28 15:29 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ZV8hYZHQHqzfx1dgOFeEVFRogSg@ifi.uio.no>
2007-06-27 14:15 ` Please release a stable kernel Linux 3.0 Bill Waddington
2007-06-28 11:15   ` Helge Hafting
2007-06-28 15:28     ` William D Waddington [this message]
2007-06-28 16:30       ` Alan Cox
2007-06-28 16:39         ` William D Waddington
2007-06-29  0:00           ` Alan Cox
2007-06-28 21:39         ` Al Viro
2007-06-28 22:00         ` Rene Herman
2007-06-28 22:48           ` Alan Cox
2007-06-28 22:45             ` Rene Herman
     [not found] <8AH0j-3Qc-11@gated-at.bofh.it>
     [not found] ` <8AH0j-3Qc-9@gated-at.bofh.it>
     [not found]   ` <8B0vZ-r6-5@gated-at.bofh.it>
     [not found]     ` <8B46G-69z-15@gated-at.bofh.it>
     [not found]       ` <8B52G-7C9-5@gated-at.bofh.it>
     [not found]         ` <8BalK-7Ic-39@gated-at.bofh.it>
     [not found]           ` <8BaYr-8tJ-17@gated-at.bofh.it>
2007-06-29 21:05             ` Bodo Eggert
2007-06-29 21:27               ` Rene Herman
2007-06-30  2:11                 ` Daniel Hazelton
2007-06-30 10:50                   ` Rene Herman
2007-06-27 13:53 Al Boldi
2007-06-27 15:52 ` Adrian Bunk
2007-06-27 16:08   ` Chuck Ebbert
2007-06-27 16:26     ` Dmitry Torokhov
2007-06-27 16:26     ` Adrian Bunk
2007-06-27 22:32   ` Al Boldi
2007-06-27 17:11 ` Al Viro
2007-06-27 22:32   ` Al Boldi
2007-06-27 23:12     ` Al Viro
2007-06-28 15:37       ` Al Boldi
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:49 Zoltán HUBERT
2007-06-21 21:54 ` Chuck Ebbert
2007-06-21 22:08 ` Alan Cox
2007-06-21 22:21   ` Zoltán HUBERT
2007-06-22 20:54     ` Willy Tarreau
2007-06-21 22:29 ` Jesper Juhl
2007-06-21 22:34   ` Chuck Ebbert
2007-06-21 23:01     ` Lennart Sorensen
2007-06-21 23:08       ` Chuck Ebbert
2007-06-21 23:36         ` Måns Rullgård
2007-06-21 23:45         ` Arjan van de Ven
2007-06-28 21:15           ` Pavel Machek
2007-06-29 13:41             ` Rafael J. Wysocki
2007-06-29 22:33               ` Pavel Machek
2007-06-22 15:00     ` Rafael J. Wysocki
2007-06-22 17:11       ` Chuck Ebbert
2007-06-22 22:10         ` Rafael J. Wysocki
2007-06-24 20:54         ` Rafael J. Wysocki
2007-06-25 16:38           ` Chuck Ebbert
2007-06-25 23:20             ` Rafael J. Wysocki
2007-06-25 23:23               ` Chuck Ebbert
2007-06-21 22:57   ` Zoltán HUBERT
2007-06-21 23:07     ` Jesper Juhl
2007-06-21 23:23     ` Lennart Sorensen
2007-06-22  8:34     ` Bernd Petrovitsch
2007-06-26 11:59     ` Helge Hafting
2007-06-26 14:37       ` Zoltán HUBERT
2007-06-26 15:04         ` Renato S. Yamane
2007-06-26 19:03         ` Roland Kuhn
2007-06-27  9:18           ` Zoltán HUBERT
2007-06-27  9:54             ` Alan McKinnon
2007-06-27  9:55             ` Al Viro
2007-06-27 14:44             ` Helge Hafting
2007-06-27 16:13             ` Chuck Ebbert
2007-06-29 16:37             ` Gerhard Mack
2007-06-21 23:30   ` Jan Engelhardt
2007-06-21 23:32     ` david
2007-06-22  8:41       ` Jan Engelhardt
2007-06-21 22:52 ` Stefan Richter
2007-06-21 22:59   ` Zoltán HUBERT
2007-06-21 22:58 ` Rene Herman
2007-06-22  3:51 ` Rik van Riel
2007-06-22  9:19 ` Xavier Bestel
2007-06-22  9:45   ` Bernd Petrovitsch
2007-06-23  7:25 ` Chris Snook

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=4683D3B0.1040708@beezmo.com \
    --to=william.waddington@beezmo.com \
    --cc=a1426z@gawab.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@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.