public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Chris Wedgwood <cw@f00f.org>, Daniel Drake <dsd@gentoo.org>,
	Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>,
	Daniel Ritz <daniel.ritz@gmx.ch>,
	Jean Delvare <khali@linux-fr.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Brice Goglin <brice@myri.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Bauke Jan Douma <bjdouma@xs4all.nl>,
	Tomasz Koprowski <tomek@koprowski.org>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz, Alan Cox <alan@redhat.com>
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Mon, 11 Dec 2006 13:52:06 +0100	[thread overview]
Message-ID: <20061211125206.GK10351@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0612101721070.12500@woody.osdl.org>

On Sun, Dec 10, 2006 at 05:23:59PM -0800, Linus Torvalds wrote:
> 
> 
> On Mon, 11 Dec 2006, Adrian Bunk wrote:
> > 
> > If life was that easy...  ;-)
> 
> No. Life _is_ that easy.
> 
> If the 2.6.16 stable tree took a patch that was questionable, and we don't 
> know what the right answer to it is from the _regular_ tree, than the 
> patch violated the stable tree rules in the first place and should just be 
> reverted.
> 
> Once people know what the right answer is (and by "know", I mean: "not 
> guess") from the regular tree having been tested with it, and people 
> understanding the problem, then it can be re-instated.
> 
> But if you're just guessing, and people don't _know_ the right answer, 
> then just revert the whole questionable area.  The patch shouldn't have 
> been there in the first place.
> 
> It really _is_ that simple.
> 
> Either it's a stable tree or it isn't. 


The non-easy part is that the patch that turned out as being 
questionable was merged back in May, and that it actually fixed issues 
for some people...

Unless you can lend me a time machine for telling Greg and Chris Wr. 
that they mustn't merge this patch for 2.6.16.17, there doesn't seem to 
be any regression free solution available at the moment.


> 		Linus


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-12-11 12:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 13:24 RFC: PCI quirks update for 2.6.16 Adrian Bunk
2006-12-07 13:53 ` Sergey Vlasov
2006-12-07 17:27   ` Bauke Jan Douma
2006-12-07 18:32     ` Sergey Vlasov
2006-12-08 15:34       ` Adrian Bunk
2006-12-07 14:38 ` Daniel Drake
2006-12-07 14:57   ` Adrian Bunk
2006-12-07 16:37     ` Alan Cox
2006-12-10  4:09   ` Sergio Monteiro Basto
2006-12-10 16:00     ` Adrian Bunk
2006-12-10 16:22       ` Daniel Drake
2006-12-10 22:33         ` Chris Wedgwood
2006-12-10 22:39           ` Linus Torvalds
2006-12-10 22:49             ` Chris Wedgwood
2006-12-11  1:17               ` Linus Torvalds
2006-12-10 23:47             ` Adrian Bunk
2006-12-11  1:23               ` Linus Torvalds
2006-12-11 12:52                 ` Adrian Bunk [this message]
2006-12-19  6:08               ` Sergio Monteiro Basto
2006-12-11  1:42       ` Sergio Monteiro Basto
2006-12-11 12:41         ` Adrian Bunk
2006-12-11 12:48           ` Sergio Monteiro Basto
2006-12-11 13:01             ` Adrian Bunk
2006-12-07 19:54 ` Jean Delvare
2006-12-07 20:45   ` Tomek Koprowski
2006-12-08 15:42     ` Adrian Bunk
2006-12-08 16:11 ` RFC: PCI quirks update for 2.6.16 (v2) Adrian Bunk
2006-12-08 21:02 ` RFC: PCI quirks update for 2.6.16 Brice Goglin

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=20061211125206.GK10351@stusta.de \
    --to=bunk@stusta.de \
    --cc=alan@redhat.com \
    --cc=bjdouma@xs4all.nl \
    --cc=bjorn.helgaas@hp.com \
    --cc=brice@myri.com \
    --cc=cw@f00f.org \
    --cc=daniel.ritz@gmx.ch \
    --cc=dsd@gentoo.org \
    --cc=gregkh@suse.de \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linville@tuxdriver.com \
    --cc=sergio@sergiomb.no-ip.org \
    --cc=tomek@koprowski.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox