kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] module_refcounting and anonymous inodes
Date: Mon, 08 Dec 2008 13:57:14 +0200	[thread overview]
Message-ID: <493D0B9A.9000401@redhat.com> (raw)
In-Reply-To: <200812081251.14648.borntraeger@de.ibm.com>

Christian Borntraeger wrote:
> Am Dienstag, 2. Dezember 2008 schrieb Christian Borntraeger:
>   
>> Hello Avi,
>>
>> here is the latest respin of my fixes for the kvm module unload problem:
>>
>> [PATCH 1/2] anon_inodes: use fops->owner for module refcount
>> [PATCH 2/2] kvm: set owner of cpu and vm file operations
>>     
>
> In the meantime patch 2 has a offset against the latest git. Should I resend
> the patch or will you apply it anyway?
>   

Applied the patches; thanks for the reminder.

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


  reply	other threads:[~2008-12-08 11:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 10:14 [PATCH 0/2] module_refcounting and anonymous inodes Christian Borntraeger
2008-12-02 10:16 ` [PATCH 1/2] anon_inodes: use fops->owner for module refcount Christian Borntraeger
2008-12-02 10:17 ` [PATCH 2/2] kvm: set owner of cpu and vm file operations Christian Borntraeger
2008-12-08 11:51 ` [PATCH 0/2] module_refcounting and anonymous inodes Christian Borntraeger
2008-12-08 11:57   ` Avi Kivity [this message]
2008-12-09  9:43     ` Sheng Yang
2008-12-09  9:51       ` Avi Kivity
2008-12-09 10:08         ` Christian Borntraeger
2008-12-09 10:15           ` Avi Kivity
2008-12-09 13:22             ` Avi Kivity
2008-12-10  2:05               ` Sheng Yang
2008-12-10  9:12                 ` Avi Kivity

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=493D0B9A.9000401@redhat.com \
    --to=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).