mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stefan Rompf <stefan@loplof.de>
Cc: Felix von Leitner <felix-linuxkernel@fefe.de>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10
Date: Sat, 12 Mar 2005 12:34:15 -0800	[thread overview]
Message-ID: <20050312203415.GB11865@kroah.com> (raw)
In-Reply-To: <200503121124.17295.stefan@loplof.de>

On Sat, Mar 12, 2005 at 11:24:16AM +0100, Stefan Rompf wrote:
> Hi,
> 
> Felix von Leitner wrote:
> 
> > Did I mention that I'm really tired of you putting stones into ATI's
> > way?  You might believe you have a right to piss everyone off, after all
> > people get what they paid for.  Or maybe you think you are on a crusade
> > to promote open source software.  But if you keep alienating me (I'm a
> > software developer) like this, I spend more time working around this
> > bullshit and less time writing free software.  In the end, everyone
> > loses.  I sincerely hope some day you people are done pissing in the
> > pool and can create at least some semblance of semi-stable APIs.  This
> > house is never going to be safe for living until you stop digging around
> > the foundation.
> 
> I cannot agree more. Many developers and maintainers say they don't care about 
> binary modules - but I do have the impression a few of them care a lot by 
> doing changes in a way that they break the current NVIDIA drivers on every 
> new kernel release.

Oh no, our secret is out!  :)

> As I read now, it seems to be the same way with ATI. Even GPL drivers
> developed outside the kernel are disfigured over and over with #ifdefs
> on KERNEL_VERSION.

Then get those GPL drivers into the kernel tree, and that will not be
needed at all.

> While I fully understand that no developer wants to support binary modules, I 
> would appreciate a little less hostile behaviour. And btw., instable API 
> leads to an instable kernel because not everyone can follow the changes.

Please read Documentation/stable_api_nonesense.txt for more info on
exactly _why_ the kernel changes like this.

thanks,

greg k-h

  reply	other threads:[~2005-03-13  0:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 10:24 Stefan Rompf
2005-03-12 20:34 ` Greg KH [this message]
     [not found] <3GZyA-16B-17@gated-at.bofh.it>
2005-03-12  5:06 ` Robert Hancock
2005-03-12  5:19   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 20:21 Felix von Leitner
2005-03-12  1:32 ` Andrew Morton
2005-03-13 21:30   ` Felix von Leitner
2005-03-12  1:33 ` Andrew Morton
2005-03-22  0:33   ` Andrew Morton
2005-03-22  2:18     ` Johannes Stezenbach
2005-03-22 16:22       ` Johannes Stezenbach
2005-03-12  1:35 ` Andrew Morton
2005-03-12  3:54   ` Adam Belay
2005-03-22  0:32     ` Andrew Morton
2005-03-22  1:20       ` Adam Belay
2005-03-22 22:29         ` Felix von Leitner
2005-03-24 23:33           ` Jeremy Fitzhardinge
2005-03-25  0:17             ` Felix von Leitner
2005-03-25 13:37         ` Bruno Ducrot
2005-03-13 21:31   ` Felix von Leitner
2005-03-12  3:51 ` Adam Belay

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=20050312203415.GB11865@kroah.com \
    --to=greg@kroah.com \
    --cc=felix-linuxkernel@fefe.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@loplof.de \
    /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

all inboxes | Powered by JetHome®