All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Schmiedehausen <hps@intermeta.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: What exactly does "supports Linux" mean?
Date: 14 May 2003 17:58:03 +0200	[thread overview]
Message-ID: <1052927883.18046.86.camel@forge.intermeta.de> (raw)
In-Reply-To: <20030514144443.GA7203@suse.de>

Using a "2.5.xxx" number was a bad example. Consider it replaced by
"2.4.17" and "2.4.18". 



	Regards
		Henning


On Wed, 2003-05-14 at 16:44, Dave Jones wrote:
> On Wed, May 14, 2003 at 02:09:33PM +0000, Henning P. Schmiedehausen wrote:
> 
>  > >From a user land perspective, only major Linux vendors or
>  > organizations could enforce such a logo program, it would cost wads of
>  > cash and it will really suck if you currently run the certification
>  > process for Linux 2.5.102 for your driver and right before you're
>  > done, 2.5.103 is released and you have to start all over again.
> 
> Certifying anything against a development series kernel is completely
> pointless.  Breakage outside the driver itself could have adverse
> affects. Example: For the last dozen or so kernels, the i845 AGP driver
> crashed on exiting X. Turned out to be a VM bug.
> 
> 
> 		Dave
-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire


  reply	other threads:[~2003-05-14 15:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 15:12 What exactly does "supports Linux" mean? Chuck Ebbert
2003-05-13 20:36 ` Måns Rullgård
2003-05-14  2:12   ` jw schultz
2003-05-14  7:57     ` Riley Williams
2003-05-14 17:58       ` Måns Rullgård
2003-05-17 16:05         ` Pavel Machek
2003-05-18  1:39           ` jw schultz
2003-05-18  3:53             ` Werner Almesberger
2003-05-18 21:49             ` Pavel Machek
2003-05-18 22:20               ` Neale Banks
2003-05-19 10:20                 ` Helge Hafting
2003-05-14 14:11     ` Henning P. Schmiedehausen
2003-05-14 15:29       ` Mike Dresser
2003-05-15  0:11       ` jw schultz
2003-05-14 14:09   ` Henning P. Schmiedehausen
2003-05-14 14:44     ` Dave Jones
2003-05-14 15:58       ` Henning Schmiedehausen [this message]
2003-05-14 16:14         ` Dave Jones
2003-05-14 19:40       ` David Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:16 Stephan von Krawczynski
2003-05-13 12:53 ` Alan Cox
2003-05-13 14:24   ` Richard B. Johnson
2003-05-13 15:07     ` Lionel Bouton
2003-05-13 16:45   ` Jonathan Matthews
2003-05-13 13:46 ` Duncan Sands

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=1052927883.18046.86.camel@forge.intermeta.de \
    --to=hps@intermeta.de \
    --cc=davej@codemonkey.org.uk \
    --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.