All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: gene.heskett@verizon.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11.1
Date: Mon, 07 Mar 2005 17:18:20 +0000	[thread overview]
Message-ID: <1110215898.3072.65.camel@localhost.localdomain> (raw)
In-Reply-To: <1110060362.12513.48.camel@mindpipe>

On Sad, 2005-03-05 at 22:06, Lee Revell wrote:
> Driver updates are a hard problem.  Nothing annoys users more than
> unsupported hardware.  But if you aggressively add support for new
> devices you can break things that have worked for ages.

You can however plan for them in advance. Guess why the -ac tree has an
ide
option to grab any otherwise unknown ide controller and stuff it in bios
tuned
DMA modes ?

Similarly you can generally apply "just PCI id" patches


  parent reply	other threads:[~2005-03-07 17:23 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 17:53 Linux 2.6.11.1 Greg KH
2005-03-04 17:53 ` Greg KH
2005-03-04 20:34 ` Ian Pilcher
2005-03-04 22:29   ` Greg KH
2005-03-04 20:44 ` Andrew Morton
2005-03-04 20:58   ` Greg KH
2005-03-04 21:15     ` Andrew Morton
2005-03-04 21:43       ` Greg KH
2005-03-04 21:54         ` Andrew Morton
2005-03-04 22:08           ` Greg KH
2005-03-04 21:53       ` Linus Torvalds
2005-03-04 21:59         ` Andrew Morton
2005-03-04 22:05           ` Greg KH
2005-03-04 22:36             ` Andrew Morton
2005-03-05  0:06               ` Greg KH
2005-03-05  0:28                 ` Linus Torvalds
2005-03-05  7:53                   ` Dave Jones
2005-03-06  5:05                     ` Greg KH
2005-03-05  1:37                 ` Jeff Garzik
2005-03-06  5:03                   ` Greg KH
2005-03-05  9:51             ` Russell King
2005-03-05 17:19               ` Jeff Garzik
2005-03-05 17:40                 ` Linus Torvalds
2005-03-05 17:46                   ` Russell King
2005-03-05 21:17                     ` Linus Torvalds
2005-03-05 21:49                       ` Gene Heskett
2005-03-05 22:06                         ` Lee Revell
2005-03-05 23:26                           ` Gene Heskett
2005-03-07 17:18                           ` Alan Cox [this message]
2005-03-08 20:16                             ` Lee Revell
2005-03-05 17:50                   ` Jeff Garzik
2005-03-05 18:22                   ` Randy.Dunlap
2005-03-05  0:24       ` Jeff Garzik
2005-03-04 21:15   ` Trond Myklebust
2005-03-04 21:33   ` Jeff Garzik
2005-03-04 21:51     ` Andrew Morton
2005-03-04 21:58       ` Jeff Garzik
2005-03-05  7:11         ` James Bourne
2005-03-08 22:07     ` Bill Davidsen
2005-03-08 22:41       ` Chris Wright
2005-03-04 21:50   ` Dave Jones
2005-03-04 23:35   ` Andries Brouwer
2005-03-04 20:48 ` Steven Rostedt
2005-03-04 20:53   ` Greg KH
2005-03-04 21:02     ` Steven Rostedt
2005-03-05 18:32 ` L. A. Walsh
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:28 Paolo
2005-03-04 19:55 ` Greg KH
2005-03-04 20:01   ` Paolo
2005-03-04 20:00 ` Jeff Garzik
2005-03-05  6:16 Shawn Starr
2005-03-06  5:06 ` Greg KH
2005-03-07  4:01   ` Shawn Starr
2005-03-07  3:58     ` Randy.Dunlap

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=1110215898.3072.65.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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 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.