From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Machek <pavel@suse.cz>, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] x86 ACPI: normalize segment descriptor register on resume
Date: Thu, 26 Jun 2008 10:56:06 +0200 [thread overview]
Message-ID: <200806261056.07180.rjw@sisk.pl> (raw)
In-Reply-To: <20080626085110.GA18599@elte.hu>
On Thursday, 26 of June 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > On Thursday, 26 of June 2008, Ingo Molnar wrote:
> > >
> > > * Andrew Morton <akpm@linux-foundation.org> wrote:
> > >
> > > > Len seems to think that Rafael seems to think that Ingo seems to think
> > > > that this patch broke one of his boxes.
> > > >
> > > > Is it so?
> > >
> > > No! :-)
> > >
> > > it found a pre-existing suspend+resume breakage on a testbox. (I.e.
> > > the debug patch worked as i'd expect it to work. Every good debug
> > > patch starts its lifetime with a sharp spike of breakages it finds.)
> >
> > Does it mean that the $subject patch doesn't break your test box after
> > all?
>
> it doesnt break it - i get the same suspend+resume breakage without that
> patch as well, if i do it manually.
Okay, so I think the $subject patch is good to go, then.
Thanks,
Rafael
next prev parent reply other threads:[~2008-06-26 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 21:03 [PATCH] x86 ACPI: normalize segment descriptor register on resume Rafael J. Wysocki
2008-06-24 21:46 ` Pavel Machek
2008-06-25 17:01 ` Ingo Molnar
2008-06-25 20:17 ` Rafael J. Wysocki
2008-06-26 8:17 ` Andrew Morton
2008-06-26 8:29 ` Ingo Molnar
2008-06-26 8:39 ` Rafael J. Wysocki
2008-06-26 8:51 ` Ingo Molnar
2008-06-26 8:56 ` Rafael J. Wysocki [this message]
2008-06-26 8:35 ` Rafael J. Wysocki
2008-06-24 21:47 ` Len Brown
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=200806261056.07180.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
/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