From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [PATCH] 2.6.21 - VMI logic error
Date: Fri, 13 Apr 2007 16:32:39 +0200 [thread overview]
Message-ID: <200704131632.39464.ak@suse.de> (raw)
In-Reply-To: <461EEADE.8060400@vmware.com>
On Friday 13 April 2007 04:28:46 Zachary Amsden wrote:
> So there is a logic error that would prevent us from ever using NOP
> relocations, thus stopping any unnecessary callouts into a VMI ROM. It
> doesn't affect us so much, but could conceivably affect open source
> implementations of a VMI ROM in the future. It is not absolutely
> critical, but it would be extremely nice to get it fixed in 2.6.21 so
> there are no broken older kernels floating around that mandate having a
> workaround for this or else breaking compatibility with these kernels.
Patch is fine for me.
-Andi
prev parent reply other threads:[~2007-04-13 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 2:28 [PATCH] 2.6.21 - VMI logic error Zachary Amsden
2007-04-13 14:32 ` Andi Kleen [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=200704131632.39464.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=aliguori@us.ibm.com \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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 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.