All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jean Delvare <khali@linux-fr.org>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.30-pre1
Date: Sun, 24 Sep 2006 00:58:38 +0200	[thread overview]
Message-ID: <20060923225838.GJ5566@stusta.de> (raw)
In-Reply-To: <1159051675.1097.194.camel@mindpipe>

On Sat, Sep 23, 2006 at 06:47:54PM -0400, Lee Revell wrote:
> On Sun, 2006-09-24 at 00:33 +0200, Adrian Bunk wrote:
> > the main goals for 2.6.16 are:
> > - no regressions
> > - security fixes
> > 
> > And I did always say that things like adding new PCI IDs are
> > considered 
> > OK for 2.6.16. 
> 
> I think the point that people are trying to make is that adding new PCI
> IDs carries an inherent risk of regression.  Unless you have access to
> every device with that ID for regression testing it could be the
> difference between a machine where one device doesn't work and a machine
> that locks up hard.

"a machine that locks up hard" is a pretty uncommon case, and it should 
be ruled out by the following two factors:
- patch must be in Linus' tree
- I'm asking the patch authors and maintainers of the affected subsystem
  whether the patch is OK for 2.6.16

You never achieve 0% risk, but many bug fixes have a much higher risk of 
regression.

I do know that the only value of the 2.6.16 tree lies in a lack of 
regressions and act accordingly, and as soon as people will report 
regressions compared to earlier 2.6.16 kernels I'll know that I'll have 
done something wrong (but I haven't yet gotten such bug reports).

> Lee

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-09-23 22:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 22:23 Linux 2.6.16.30-pre1 Adrian Bunk
2006-09-22 22:38 ` Greg KH
2006-09-22 22:47   ` Adrian Bunk
2006-09-22 23:09     ` Greg KH
2006-09-23  4:56       ` Willy Tarreau
2006-09-23 23:21         ` Adrian Bunk
2006-09-23 23:53           ` Willy Tarreau
2006-09-24  7:46             ` Sergey Vlasov
2006-09-24 18:16             ` Adrian Bunk
2006-09-24 19:46               ` Stefan Richter
2006-09-24 19:44                 ` Willy Tarreau
2006-09-24 20:02               ` Willy Tarreau
2006-09-25  1:01                 ` Adrian Bunk
2006-09-24 10:17           ` Pavel Machek
2006-09-25  1:23             ` Adrian Bunk
2006-09-25  8:15               ` Pavel Machek
2006-09-27  5:14               ` Greg KH
2006-09-23 20:49       ` Jean Delvare
2006-09-23 20:57         ` Lee Revell
2006-09-23 21:20           ` Jean Delvare
2006-09-23 22:47             ` Adrian Bunk
2006-09-23 22:33         ` Adrian Bunk
2006-09-23 22:47           ` Lee Revell
2006-09-23 22:58             ` Adrian Bunk [this message]
2006-09-23 22:12       ` Adrian Bunk
2006-09-24 10:12     ` Pavel Machek
2006-09-25  1:20       ` Adrian Bunk
2006-09-24 20:25 ` Grant Coady

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=20060923225838.GJ5566@stusta.de \
    --to=bunk@stusta.de \
    --cc=greg@kroah.com \
    --cc=khali@linux-fr.org \
    --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.