public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Hugh Dickins <hugh@veritas.com>,
	"Michael S. Tsirkin" <mst@mellanox.co.il>,
	Pavel Machek <pavel@suse.cz>, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	len.brown@intel.com, linux-acpi@vger.kernel.org,
	linux-pm@osdl.org, Martin Lorenz <martin@lorenz.eu.org>,
	Andi Kleen <ak@suse.de>,
	discuss@x86-64.org, linux-serial@vger.kernel.org,
	linux-thinkpad@linux-thinkpad.org,
	Ernst Herzberg <earny@net4u.de>
Subject: Re: 2.6.19-rc <-> ThinkPads, summary
Date: Sun, 5 Nov 2006 07:23:30 +0100	[thread overview]
Message-ID: <20061105062330.GT13381@stusta.de> (raw)
In-Reply-To: <20061104140440.GB19760@flint.arm.linux.org.uk>

On Sat, Nov 04, 2006 at 02:04:40PM +0000, Russell King wrote:
> On Sat, Nov 04, 2006 at 04:49:07AM +0100, Adrian Bunk wrote:
> > As far as I can see, the 2.6.19-rc ThinkPad situation is still 
> > confusing and we don't even know how many different bugs we are 
> > chasing...
> 
> Why am I copied on this?  Nothing jumps out as being in any area of my
> interest (which today is limited to ARM architecture only.)

Ernst bisected his problem to your
commit 1fbbac4bcb03033d325c71fc7273aa0b9c1d9a03 
("serial_cs: convert multi-port table to quirk table").

It might be a false positive of the bisecting, but if it turns out to 
actually cause problems it was your commit.

> Russell King

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-11-05  6:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061029231358.GI27968@stusta.de>
2006-10-30 13:56 ` 2.6.19-rc3: known unfixed regressions (v3) Michael S. Tsirkin
2006-10-30 15:27   ` Martin Lorenz
2006-10-30 16:17   ` Jun'ichi Nomura
2006-10-30 16:32     ` Michael S. Tsirkin
2006-10-30 17:20       ` Jun'ichi Nomura
2006-10-30 17:54         ` Michael S. Tsirkin
2006-10-30 16:44     ` Linus Torvalds
2006-10-30 17:34       ` Jun'ichi Nomura
2006-10-30 18:16         ` Linus Torvalds
2006-10-30 18:35           ` Adrian Bunk
2006-10-30 19:00             ` Michael S. Tsirkin
2006-10-30 19:06             ` Hugh Dickins
2006-10-31 12:47             ` Martin Lorenz
2006-10-30 18:58           ` Michael S. Tsirkin
2006-10-31 21:15           ` Michael S. Tsirkin
2006-11-01  3:01   ` 2.6.19-rc <-> ThinkPads Adrian Bunk
2006-11-01  3:15     ` Len Brown
2006-11-01  5:11       ` Ernst Herzberg
2006-11-01  5:26         ` Linus Torvalds
2006-11-01  5:54           ` Michael S. Tsirkin
2006-11-01  6:16             ` Linus Torvalds
2006-11-01 17:25               ` Andi Kleen
2006-11-01 18:12                 ` Michael S. Tsirkin
2006-11-01 18:25                 ` Linus Torvalds
2006-11-01 19:33                   ` Michael S. Tsirkin
2006-11-01 19:44                     ` Linus Torvalds
2006-11-01 19:34                   ` Andi Kleen
2006-11-01 19:52                     ` Linus Torvalds
2006-11-01 21:15                       ` Andi Kleen
2006-11-01 22:35               ` Bill Davidsen
2006-11-01  6:18             ` Michael S. Tsirkin
2006-11-01  9:33               ` Pavel Machek
2006-11-01 12:02                 ` Michael S. Tsirkin
2006-11-01 17:17               ` Andi Kleen
2006-11-01 13:50           ` Stefan Seyfried
2006-11-01 16:36     ` Hugh Dickins
2006-11-04  3:49     ` 2.6.19-rc <-> ThinkPads, summary Adrian Bunk
2006-11-04 13:51       ` Hugh Dickins
2006-11-04 14:04       ` Russell King
2006-11-05  6:23         ` Adrian Bunk [this message]
2006-11-17  1:53       ` 2.6.19-rc <-> ThinkPads, (related Ubuntu bug report) Mark Stosberg

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=20061105062330.GT13381@stusta.de \
    --to=bunk@stusta.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=earny@net4u.de \
    --cc=hugh@veritas.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-thinkpad@linux-thinkpad.org \
    --cc=martin@lorenz.eu.org \
    --cc=mst@mellanox.co.il \
    --cc=pavel@suse.cz \
    --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