kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	eric.auger@st.com, eric.auger@linaro.org, joro@8bytes.org,
	avi.kivity@gmail.com, feng.wu@intel.com
Subject: Re: [PATCH] virt: IRQ bypass manager
Date: Mon, 13 Jul 2015 12:37:24 -0600	[thread overview]
Message-ID: <1436812644.1391.375.camel@redhat.com> (raw)
In-Reply-To: <55A0348F.606@redhat.com>

On Fri, 2015-07-10 at 23:09 +0200, Paolo Bonzini wrote:
> 
> On 10/07/2015 19:52, Alex Williamson wrote:
> > Perhaps if a second consumer comes along that would be justification for
> > tying it elsewhere in the build system.  ARM will obviously need to do
> > similar.  Are there better options?
> > 
> > Also, there's no maintainer for the top level virt/ directory.  Paolo,
> > would you feel comfortable taking this, maybe with some additional acks?
> 
> That's okay; alternatively, we can share it since after all you wrote
> most of it.

Sure.  Actually my wording was confusing, I was actually just suggesting
the patch be merged through the KVM tree since I think the consumer code
is going to be significantly bulkier than the producer code.  I can
certainly add a MAINTAINERS entry for virt/lib/ that we can share if you
like.  Thanks,

Alex

  reply	other threads:[~2015-07-13 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 17:52 [PATCH] virt: IRQ bypass manager Alex Williamson
2015-07-10 21:09 ` Paolo Bonzini
2015-07-13 18:37   ` Alex Williamson [this message]
2015-07-13 15:32 ` Eric Auger
2015-07-13 18:25   ` Alex Williamson
2015-07-13 20:58     ` Eric Auger
2015-07-13 21:31       ` Alex Williamson

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=1436812644.1391.375.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=avi.kivity@gmail.com \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=feng.wu@intel.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 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).