From: "H. Peter Anvin" <hpa@zytor.com>
To: Takao Indoh <indou.takao@jp.fujitsu.com>,
amwang@redhat.com, dyoung@redhat.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
xiyou.wangcong@gmail.com, rjw@sisk.pl, yinghai.lu@oracle.com,
tiwai@suse.de, kexec@lists.infradead.org
Cc: Tejun Heo <tj@kernel.org>, Takashi Iwai <tiwai@suse.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] x86: revert "x86: Fix S4 regression"
Date: Sat, 11 Aug 2012 11:34:22 -0700 [thread overview]
Message-ID: <5026A5AE.6050608@zytor.com> (raw)
In-Reply-To: <20120811182644.GA1787@cantor.Home>
On 08/11/2012 11:26 AM, Jerry Snitselaar wrote:
>>
>> This patch from Jacob Shin solves the problem, and seems like it might
>> be a better solution.
>>
>> [PATCH 2/5] x86: find_early_table_space based on memory ranges that
>> are being mapped
>>
>> https://lkml.org/lkml/2012/8/9/540
>>
> Actually, apply that series of 5 patches.
>
I was hoping Tejun would comment on it, but I think I'll pull it into -tip.
However, the real question is what we should do for -stable; applying
the full patch series seems a big aggressive for that. On the other
hand, if it really is The Right Thing then perhaps we should do so anyway.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-08-11 18:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 5:21 [PATCH] x86: revert "x86: Fix S4 regression" Cong Wang
2012-06-15 11:11 ` Cong Wang
2012-06-15 12:15 ` Takashi Iwai
2012-06-15 19:09 ` Rafael J. Wysocki
2012-06-18 3:10 ` Cong Wang
2012-07-17 3:15 ` Takao Indoh
2012-07-23 10:00 ` Dave Young
2012-07-23 11:22 ` Takao Indoh
2012-07-23 12:51 ` Dave Young
2012-07-24 15:55 ` Cong Wang
2012-07-25 0:19 ` Takao Indoh
2012-08-06 20:42 ` Vivek Goyal
2012-08-06 21:55 ` Yinghai Lu
2012-08-11 17:57 ` Jerry Snitselaar
2012-08-11 18:26 ` Jerry Snitselaar
2012-08-11 18:34 ` H. Peter Anvin [this message]
2012-08-11 18:39 ` H. Peter Anvin
2012-08-11 19:33 ` Tejun Heo
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=5026A5AE.6050608@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=dyoung@redhat.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yinghai.lu@oracle.com \
/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