From: Zhang Rui <rui.zhang@intel.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Ingo Molnar <mingo@elte.hu>, Matthew Garrett <mjg@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Huang Ying <huang.ying.caritas@gmail.com>
Subject: Re: [PATCH v4] x86, efi: Calling __pa() with an ioremap'd address is invalid
Date: Wed, 07 Dec 2011 08:36:23 +0800 [thread overview]
Message-ID: <1323218183.9574.1434.camel@rui> (raw)
In-Reply-To: <1323092402.4838.6.camel@mfleming-mobl1.ger.corp.intel.com>
On Mon, 2011-12-05 at 21:40 +0800, Matt Fleming wrote:
> On Mon, 2011-12-05 at 13:32 +0100, Ingo Molnar wrote:
> > * Matt Fleming <matt@console-pimps.org> wrote:
> >
> > > Zhang, it'd be good to make sure that this still actually
> > > fixes your problem on CONFIG_X86_32. Also, if anyone has a
> > > Macbook Pro/Macbook Air, please make sure that this patch
> > > doesn't cause your machine to reboot/hang, as those machines
> > > tend to be the ones that this problem.
> >
> > Ping - has it been tested on an affected box, can we apply it to
> > the x86 tree?
>
> I've not had any response from Zhang or anyone with a macbook. So as far
> as I know, no, this v4 patch hasn't been tested on any of the affected
> machines.
>
> Zhang, could you test this patch, please? Or pass it along to someone
> else who can do the testing. Thanks.
>
Sure.
I can test it tomorrow because I'm in a training these two days.
thanks,
rui
next prev parent reply other threads:[~2011-12-07 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 13:09 [PATCH v4] x86, efi: Calling __pa() with an ioremap'd address is invalid Matt Fleming
2011-12-05 12:32 ` Ingo Molnar
2011-12-05 13:40 ` Matt Fleming
2011-12-07 0:36 ` Zhang Rui [this message]
2011-12-08 12:47 ` Matt Fleming
2011-12-09 20:08 ` [tip:x86/urgent] x86, efi: Calling __pa() with an ioremap()ed " tip-bot for Matt Fleming
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=1323218183.9574.1434.camel@rui \
--to=rui.zhang@intel.com \
--cc=hpa@zytor.com \
--cc=huang.ying.caritas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.