From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Dmitry Adamushko
<dmitry.adamushko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>,
Andreas Mohr <andi-5+Cda9B46AM@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch] Re: [Bug #12100] resume (S2R) broken by Intel microcode module, on A110L
Date: Sat, 20 Dec 2008 00:30:06 +0100 [thread overview]
Message-ID: <20081219233006.GA17984@elte.hu> (raw)
In-Reply-To: <1229728524.5122.13.camel@earth>
* Dmitry Adamushko <dmitry.adamushko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi,
>
>
> This is in response to the following bug report:
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12100
> Subject : resume (S2R) broken by Intel microcode module, on A110L
> Submitter : Andreas Mohr <andi-5+Cda9B46AM@public.gmane.org>
> Date : 2008-11-25 08:48 (19 days old)
> Handled-By : Dmitry Adamushko <dmitry.adamushko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
applied to tip/x86/microcode, thanks Dmitry!
The fix looks right but somewhat intrusive in scope, so i'm a bit
reluctant to push it towards .28 straight away - without having feedback
in the bugzilla. If feedback is positive (the bug reported there goes away
completely) we can cherry-pick it over into x86/urgent, ok? And in any
case i've marked it as a -stable backport for .28.1.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Andreas Mohr <andi@lisas.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [patch] Re: [Bug #12100] resume (S2R) broken by Intel microcode module, on A110L
Date: Sat, 20 Dec 2008 00:30:06 +0100 [thread overview]
Message-ID: <20081219233006.GA17984@elte.hu> (raw)
In-Reply-To: <1229728524.5122.13.camel@earth>
* Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> Hi,
>
>
> This is in response to the following bug report:
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12100
> Subject : resume (S2R) broken by Intel microcode module, on A110L
> Submitter : Andreas Mohr <andi@lisas.de>
> Date : 2008-11-25 08:48 (19 days old)
> Handled-By : Dmitry Adamushko <dmitry.adamushko@gmail.com>
applied to tip/x86/microcode, thanks Dmitry!
The fix looks right but somewhat intrusive in scope, so i'm a bit
reluctant to push it towards .28 straight away - without having feedback
in the bugzilla. If feedback is positive (the bug reported there goes away
completely) we can cherry-pick it over into x86/urgent, ok? And in any
case i've marked it as a -stable backport for .28.1.
Ingo
next prev parent reply other threads:[~2008-12-19 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 23:15 [patch] Re: [Bug #12100] resume (S2R) broken by Intel microcode module, on A110L Dmitry Adamushko
2008-12-19 23:15 ` Dmitry Adamushko
2008-12-19 23:30 ` Ingo Molnar [this message]
2008-12-19 23:30 ` Ingo Molnar
[not found] ` <20081219233006.GA17984-X9Un+BFzKDI@public.gmane.org>
2009-01-11 14:56 ` Ingo Molnar
2009-01-11 14:56 ` Ingo Molnar
[not found] ` <20090111145615.GA26173-X9Un+BFzKDI@public.gmane.org>
2009-01-11 19:58 ` Dmitry Adamushko
2009-01-11 19:58 ` Dmitry Adamushko
[not found] ` <b647ffbd0901111158r467f3358wa50f6a6e92d8129f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-11 20:11 ` Mike Travis
2009-01-11 20:11 ` Mike Travis
2008-12-20 13:19 ` Andreas Mohr
2008-12-20 13:19 ` Andreas Mohr
[not found] ` <20081220131946.GA31366-p/qQFhXj4MHA4IYVXhSI5GHfThorsUsI@public.gmane.org>
2008-12-20 13:30 ` Ingo Molnar
2008-12-20 13:30 ` Ingo Molnar
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=20081219233006.GA17984@elte.hu \
--to=mingo-x9un+bfzkdi@public.gmane.org \
--cc=andi-5+Cda9B46AM@public.gmane.org \
--cc=dmitry.adamushko-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rjw-KKrjLPT3xs0@public.gmane.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.