On Monday, 25 of February 2008, Michael S. Tsirkin wrote:
> On Mon, Feb 25, 2008 at 9:46 PM, Andrew Morton
> <[EMAIL PROTECTED]> wrote:
> > On Mon, 25 Feb 2008 21:19:24 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On my T61p, 2.6.25-rc2 seems to get acpi events from keypres
Hi!
> On Monday, 25 of February 2008, Michael S. Tsirkin wrote:
> > On Mon, Feb 25, 2008 at 9:46 PM, Andrew Morton
> > <[EMAIL PROTECTED]> wrote:
> > > On Mon, 25 Feb 2008 21:19:24 +0200 "Michael S. Tsirkin" <[EMAIL
> > > PROTECTED]> wrote:
> > >
> > > > On my T61p, 2.6.25-rc2 seems to get acpi
On Mon, Feb 25, 2008 at 11:26 PM, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
>
> > On Monday, 25 of February 2008, Michael S. Tsirkin wrote:
> > > On Mon, Feb 25, 2008 at 9:46 PM, Andrew Morton
> > > <[EMAIL PROTECTED]> wrote:
> > > > On Mon, 25 Feb 2008 21:19:24 +0200 "Michael S. Tsirkin"
Pavel Machek wrote:
commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
Author: Pavel Machek <[EMAIL PROTECTED]>
Date: Thu Feb 21 13:56:55 2008 +0100
power_state: get rid of write-only variable in SATA
This is pretty unlikely to be it. Can you double check that this patch
really breaks somet
Hi!
> > > commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
> > > Author: Pavel Machek <[EMAIL PROTECTED]>
> > > Date: Thu Feb 21 13:56:55 2008 +0100
> > >
> > > power_state: get rid of write-only variable in SATA
> >
> > This is pretty unlikely to be it. Can you double check that this p
On Mon, Feb 25, 2008 at 11:50 PM, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
>
> > > > commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
> > > > Author: Pavel Machek <[EMAIL PROTECTED]>
> > > > Date: Thu Feb 21 13:56:55 2008 +0100
> > > >
> > > > power_state: get rid of write-onl
Hi!
> > > > > commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
> > > > > Author: Pavel Machek <[EMAIL PROTECTED]>
> > > > > Date: Thu Feb 21 13:56:55 2008 +0100
> > > > >
> > > > > power_state: get rid of write-only variable in SATA
> > > >
> > > > This is pretty unlikely to be i
On Mon 2008-02-25 16:32:38, Jeff Garzik wrote:
> Pavel Machek wrote:
>>> commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
>>> Author: Pavel Machek <[EMAIL PROTECTED]>
>>> Date: Thu Feb 21 13:56:55 2008 +0100
>>>
>>> power_state: get rid of write-only variable in SATA
>>
>> This is pretty unlik
On Tue, Feb 26, 2008 at 12:20 AM, Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> > > > > > commit 559bbe6cbd0d8c68d40076a5f7dc98e3bf5864b2
> > > > > > Author: Pavel Machek <[EMAIL PROTECTED]>
> > > > > > Date: Thu Feb 21 13:56:55 2008 +0100
> > > > > >
> > > > > > power_st
On Tue, 26 Feb 2008 00:36:54 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
wrote:
> > Hmm, mystery partly solved... as you guessed it, this piece of code
> > was not in my tree.
> >
> > (still, how can this cause autoresume after 5 seconds is a mystery to
> > me).
> >
> >
> >
On Tue, Feb 26, 2008 at 12:39 AM, Andrew Morton
<[EMAIL PROTECTED]> wrote:
> On Tue, 26 Feb 2008 00:36:54 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
> wrote:
>
> > > Hmm, mystery partly solved... as you guessed it, this piece of code
> > > was not in my tree.
> > >
> > > (still, how can
On Tue, 26 Feb 2008 00:48:12 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
wrote:
> On Tue, Feb 26, 2008 at 12:39 AM, Andrew Morton
> <[EMAIL PROTECTED]> wrote:
> > On Tue, 26 Feb 2008 00:36:54 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > > Hmm, mystery partly solved...
Hi!
> > > > Maybe it doesn't. Andrew saw the autoresume on -rc[2,3]
> > >
> > > And earlier - I think 2.6.23 does it as well.
> >
> > But that one at least resumes fine, does it not?
>
> Nope, the resume-after-five-seconds and black-screen-after-resume have
> always been there (I've only had t
On Tue, Feb 26, 2008 at 12:53 AM, Andrew Morton
<[EMAIL PROTECTED]> wrote:
>
> On Tue, 26 Feb 2008 00:48:12 +0200 "Michael S. Tsirkin" <[EMAIL PROTECTED]>
> wrote:
>
> > On Tue, Feb 26, 2008 at 12:39 AM, Andrew Morton
> > <[EMAIL PROTECTED]> wrote:
> > > On Tue, 26 Feb 2008 00:36:54 +0200 "Mich
14 matches
Mail list logo