From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Laurent Riffard <laurent.riffard@free.fr>,
Rajesh Shah <rajesh.shah@intel.com>,
toralf.foerster@gmx.de, Jeff Garzik <jeff@garzik.org>,
Pavel Machek <pavel@ucw.cz>, Auke Kok <auke-jan.h.kok@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: 2.6.19-rc4: known unfixed regressions
Date: Thu, 2 Nov 2006 13:29:57 -0800 [thread overview]
Message-ID: <20061102212957.GA16201@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611021240300.25218@g5.osdl.org>
On Thu, Nov 02, 2006 at 12:54:02PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 2 Nov 2006, Rafael J. Wysocki wrote:
>
> > Can we please add the following two to the list of known regressions:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=7082
>
> Ok, I think I'll just revert it.
>
> Decoding the PCI IO range is fine - even if a driver has detached, the
> kernel knows where the PCI devices are, and won't re-use the range. So
> while the patch that triggers the problem seems valid in itself, it's
> probably not worth the pain to apply it at this point. So I think I'll
> revert it - the rationale for the patch was fairly weak.
>
> Greg, or would you prefer to do the honors?
I'll queue it up.
thanks,
greg k-h
next prev parent reply other threads:[~2006-11-02 21:30 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 4:27 Linux 2.6.19-rc4 Linus Torvalds
2006-10-31 5:34 ` Andrew Morton
2006-10-31 14:43 ` Jun'ichi Nomura
2006-10-31 16:44 ` Linux 2.6.19-rc4: udev compatibility broken? Mark Lord
2006-10-31 15:55 ` Linux 2.6.19-rc4 Linus Torvalds
2006-10-31 16:14 ` Martin J. Bligh
2006-10-31 16:34 ` Ray Lee
2006-10-31 16:51 ` Dave Jones
2006-10-31 21:26 ` Valdis.Kletnieks
2006-10-31 22:39 ` Al Viro
2006-11-02 16:03 ` Valdis.Kletnieks
2006-10-31 20:53 ` Valdis.Kletnieks
2006-10-31 21:29 ` Al Viro
2006-11-01 6:33 ` Willy Tarreau
2006-11-01 20:26 ` Guennadi Liakhovetski
2006-11-01 21:04 ` Sam Ravnborg
2006-11-02 21:19 ` Guennadi Liakhovetski
2006-10-31 18:33 ` Adrian Bunk
2006-10-31 18:36 ` Martin Bligh
2006-10-31 18:54 ` Adrian Bunk
2006-10-31 18:45 ` Adrian Bunk
2006-10-31 19:26 ` Russell King
2006-10-31 19:39 ` Martin Bligh
2006-10-31 17:02 ` CONFIG_USB_USBNET and mii_* (was Re: Linux 2.6.19-rc4) Athanasius
2006-10-31 17:11 ` Randy Dunlap
2006-10-31 19:56 ` 2.6.19-rc4: known unfixed regressions Adrian Bunk
2006-10-31 19:56 ` Adrian Bunk
2006-10-31 20:11 ` Greg KH
2006-10-31 20:11 ` Greg KH
2006-11-04 3:15 ` Adrian Bunk
2006-10-31 20:12 ` Arjan van de Ven
2006-10-31 20:12 ` Arjan van de Ven
2006-10-31 20:21 ` Adrian Bunk
2006-11-02 20:02 ` Rafael J. Wysocki
2006-11-02 20:10 ` Andrew Morton
2006-11-02 21:22 ` Auke Kok
2006-11-02 21:55 ` Alan Cox
2006-11-02 20:54 ` Linus Torvalds
2006-11-02 21:29 ` Greg KH [this message]
2006-11-02 21:26 ` Adrian Bunk
2006-11-02 21:40 ` Rafael J. Wysocki
2006-10-31 20:08 ` 2.6.19-rc4: known regressions with patches Adrian Bunk
2006-11-03 2:41 ` Linux 2.6.19-rc4: known unfixed regressions (v2) Adrian Bunk
2006-11-03 2:56 ` [discuss] " Dave Jones
2006-11-03 8:25 ` Alexey Starikovskiy
2006-11-03 15:56 ` Dave Jones
2006-11-05 17:32 ` Christian
2006-11-05 20:04 ` Dave Jones
2006-11-06 17:35 ` Adrian Bunk
2006-11-06 17:49 ` Dave Jones
2006-11-06 17:49 ` Dave Jones
2006-11-06 6:00 ` Adrian Bunk
2006-11-06 15:43 ` Christian
2006-11-06 17:20 ` Dave Jones
2006-11-06 17:30 ` Adrian Bunk
2006-11-06 17:37 ` Adrian Bunk
2006-11-04 18:21 ` [linux-usb-devel] " Greg KH
2006-11-05 6:48 ` 2.6.19-rc4: known unfixed regressions (v3) Adrian Bunk
2006-11-05 6:48 ` Adrian Bunk
2006-11-05 9:30 ` Jeff Chua
2006-11-05 9:30 ` Jeff Chua
2006-11-06 17:47 ` [discuss] " Andi Kleen
2006-11-06 17:47 ` Andi Kleen
2006-11-05 13:26 ` Michael S. Tsirkin
2006-11-05 13:26 ` Michael S. Tsirkin
2006-11-05 13:57 ` Adrian Bunk
2006-11-05 15:17 ` Eric W. Biederman
2006-11-07 4:22 ` Adrian Bunk
2006-11-07 5:18 ` Bryan O'Sullivan
2006-11-07 8:50 ` Eric W. Biederman
2006-11-07 16:19 ` Bryan O'Sullivan
2006-11-07 17:33 ` Eric W. Biederman
2006-11-07 17:37 ` Dave Olson
2006-11-07 18:20 ` Eric W. Biederman
2006-11-07 20:30 ` Dave Olson
2006-11-07 20:51 ` Eric W. Biederman
2006-11-07 21:01 ` Dave Olson
2006-11-07 21:35 ` Eric W. Biederman
2006-11-07 21:41 ` Dave Olson
2006-11-07 22:25 ` Eric W. Biederman
2006-11-07 18:01 ` Bryan O'Sullivan
2006-11-07 18:29 ` Eric W. Biederman
2006-11-07 21:32 ` Bryan O'Sullivan
2006-11-07 22:00 ` Eric W. Biederman
2006-11-08 5:14 ` Bryan O'Sullivan
2006-11-08 11:11 ` Eric W. Biederman
2006-11-05 15:22 ` Eric W. Biederman
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 2:17 ` Ernst Herzberg
2006-11-07 5:41 ` Len Brown
2006-11-07 5:41 ` Len Brown
2006-11-07 20:05 ` Ernst Herzberg
2006-11-07 20:05 ` Ernst Herzberg
2006-11-08 8:36 ` [linux-pm] " Adrian Bunk
2006-11-06 12:48 ` 2.6.19-rc4: known regressions with patches (v2) Adrian Bunk
2006-11-07 13:30 ` 2.6.19-rc4: known unfixed regressions (v4) Adrian Bunk
2006-11-07 13:30 ` Adrian Bunk
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=20061102212957.GA16201@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=bunk@stusta.de \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rajesh.shah@intel.com \
--cc=rjw@sisk.pl \
--cc=toralf.foerster@gmx.de \
--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 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.