All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0 of 5] PowerPC KVM fixes for 2.6.26
Date: Sun, 25 May 2008 13:35:36 +0300	[thread overview]
Message-ID: <483940F8.2070107@qumranet.com> (raw)
In-Reply-To: <patchbomb.1211412170@localhost.localdomain>

Hollis Blanchard wrote:
> Hi Avi, these bug fixes should be committed for 2.6.26. Most are pretty
> harmless. Although the mmap_sem locking problem is fatal if you hit it, in
> practice we simply shouldn't hit that error case anyways.
>   

Thanks; applied all.  AFAICS only the locking fix is necessary for 2.6.26?


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-05-25 10:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 23:22 [PATCH 0 of 5] PowerPC KVM fixes for 2.6.26 Hollis Blanchard
2008-05-21 23:22 ` [PATCH 1 of 5] KVM: ppc: Remove duplicate function Hollis Blanchard
2008-05-21 23:22 ` [PATCH 2 of 5] KVM: ppc: add lwzx/stwz emulation Hollis Blanchard
2008-05-21 23:22 ` [PATCH 3 of 5] KVM: ppc: Remove unmatched kunmap() call Hollis Blanchard
2008-05-21 23:22 ` [PATCH 4 of 5] KVM: ppc: Use a read lock around MMU operations, and release it on error Hollis Blanchard
2008-05-21 23:22 ` [PATCH 5 of 5] [kvm powerpc] Report bad GFNs Hollis Blanchard
2008-05-22  2:47   ` Anthony Liguori
2008-05-22 14:02     ` Hollis Blanchard
2008-05-25 10:35 ` Avi Kivity [this message]
2008-05-27 15:39   ` [PATCH 0 of 5] PowerPC KVM fixes for 2.6.26 Hollis Blanchard

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=483940F8.2070107@qumranet.com \
    --to=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.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.