All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PULL REQUEST] kvm-kmod
Date: Mon, 12 Oct 2009 19:27:36 -0300	[thread overview]
Message-ID: <20091012222736.GA16855@amt.cnet> (raw)
In-Reply-To: <20091012085454.20775.12700.stgit@mchn012c.ww002.siemens.net>

On Mon, Oct 12, 2009 at 10:54:54AM +0200, Jan Kiszka wrote:
> The following changes since commit e19bf3254985d9b8b6b916acc82fc398595cff95:
>   Jan Kiszka (1):
>         x86: Remove zombie kvm_trace from build
> 
> are available in the git repository at:
> 
>   git://git.kiszka.org/kvm-kmod.git queue
> 
> Jan Kiszka (4):
>       Remove const from vm_ops to avoid warnings on older kernels
>       Add cpufreq_get wrapper for !CONFIG_CPU_FREQ
>       Avoid kmap_atomic_to_page in svm
>       Update source link
> 
>  external-module-compat-comm.h |    7 +++++++
>  linux-2.6                     |    2 +-
>  sync                          |   14 ++++++++++++++
>  3 files changed, 22 insertions(+), 1 deletions(-)

Pushed, thanks.


  parent reply	other threads:[~2009-10-12 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12  8:54 [PULL REQUEST] kvm-kmod Jan Kiszka
2009-10-12  8:54 ` [PATCH 4/4] Update source link Jan Kiszka
2009-10-12  8:54 ` [PATCH 3/4] Avoid kmap_atomic_to_page in svm Jan Kiszka
2009-10-12  8:54 ` [PATCH 2/4] Add cpufreq_get wrapper for !CONFIG_CPU_FREQ Jan Kiszka
2009-10-12  8:54 ` [PATCH 1/4] Remove const from vm_ops to avoid warnings on older kernels Jan Kiszka
2009-10-12 22:27 ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-19 10:59 [PULL REQUEST] kvm-kmod Jan Kiszka
2009-10-19 19:37 ` Marcelo Tosatti

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=20091012222736.GA16855@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --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.