From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: gleb@redhat.com, rusty@rustcorp.com.au, kvm@vger.kernel.org,
virtualization@lists.osdl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, markmc@redhat.com,
herbert.xu@redhat.com, quintela@redhat.com, dlaor@redhat.com,
avi@redhat.com
Subject: Re: [PATCH 3/3] vhost: fix get_user_pages_fast error handling
Date: Wed, 24 Feb 2010 07:37:37 +0200 [thread overview]
Message-ID: <20100224053737.GB27806@redhat.com> (raw)
In-Reply-To: <20100223.144235.08984181.davem@davemloft.net>
On Tue, Feb 23, 2010 at 02:42:35PM -0800, David Miller wrote:
>
> Just for the record I'm generally not interested in vhost
> patches.
>
> If it's a specific network one that will be merged via
> the networking tree, yes please CC: me.
>
> But if it's a bunch of changes to vhost.c and other pieces
> of infrastructure, feel free to leave me out of it. It just
> clutters my already overflowing inbox.
>
> Thanks.
Dave, so while Rusty's on vacation, what's the best way to get vhost
infrastructure fixes in? Are you ok with getting pull requests and
merging them into net-next? That should keep the clutter in your inbox
to the minimum.
Of course network changes would still go the usual way.
--
MST
next prev parent reply other threads:[~2010-02-24 5:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 16:57 [PATCH 0/3] vhost: logging fixes Michael S. Tsirkin
2010-02-23 16:57 ` [PATCH 1/3] vhost: logging math fix Michael S. Tsirkin
2010-02-23 19:26 ` Juan Quintela
2010-02-23 16:57 ` [PATCH 2/3] vhost: initialize log eventfd context pointer Michael S. Tsirkin
2010-02-23 19:31 ` Juan Quintela
2010-02-23 16:57 ` [PATCH 3/3] vhost: fix get_user_pages_fast error handling Michael S. Tsirkin
2010-02-23 17:34 ` Gleb Natapov
2010-02-23 17:32 ` Michael S. Tsirkin
2010-02-23 17:39 ` Gleb Natapov
2010-02-23 17:39 ` Michael S. Tsirkin
2010-02-23 17:43 ` Gleb Natapov
2010-02-23 22:42 ` David Miller
2010-02-24 5:37 ` Michael S. Tsirkin [this message]
2010-02-24 7:04 ` David Miller
2010-02-24 7:34 ` Michael S. Tsirkin
2010-02-24 7:41 ` David Miller
2010-02-23 19:56 ` Juan Quintela
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=20100224053737.GB27806@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=dlaor@redhat.com \
--cc=gleb@redhat.com \
--cc=herbert.xu@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=quintela@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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).