From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alex Shi <alex.shi@intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>, Len Brown <len.brown@intel.com>,
Changlong Xie <changlongx.xie@intel.com>,
linux-acpi@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
lkp@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] Commit ac3ebafa81a makes NHM EX/EP machines hung out since 3.9-rc1
Date: Tue, 02 Apr 2013 02:13:27 +0200 [thread overview]
Message-ID: <3665202.iVImCII9RK@vostro.rjw.lan> (raw)
In-Reply-To: <515396B7.1060909@intel.com>
On Thursday, March 28, 2013 09:02:47 AM Alex Shi wrote:
> On 03/28/2013 08:40 AM, Rafael J. Wysocki wrote:
> >> >
> >> > It fixes the problem on my 8 sockets Nehalem-EX that will hang around
> >> > ip_auto_config()
> >> >
> >> > Tested-by: Yinghai Lu <yinghai@kernel.org>
> >> >
> >> > Rafael,
> >> > Can you please push this one to Linus tree ?
> >> > As the offending patch was via your tree to upstream.
> > I will if there's no better way to address this issue before -rc6.
>
> If it can be pushed to upstream, please add:
>
> Reported-by: LKP project <lkp@linux.intel.com>
> Reported-by: Xie ChanglongX <changlongx.xie@intel.com>
I have applied the patch, but I've modified the changelog. Please check the
linux-next branch of my tree and see if the commit is what you meant.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-04-02 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130313022759.GA120840@bee>
[not found] ` <5152781B.6060603@intel.com>
2013-03-27 16:36 ` [LKP] Commit ac3ebafa81a makes NHM EX/EP machines hung out since 3.9-rc1 Yinghai Lu
2013-03-28 0:40 ` Rafael J. Wysocki
2013-03-28 1:02 ` Alex Shi
2013-04-02 0:13 ` Rafael J. Wysocki [this message]
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=3665202.iVImCII9RK@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=alex.shi@intel.com \
--cc=changlongx.xie@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@linux.intel.com \
--cc=yinghai@kernel.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