All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
To: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
Cc: kvm-devel <kvm@vger.kernel.org>,
	Qemu-development List <qemu-devel@nongnu.org>,
	V9FS Developers <v9fs-developer@lists.sourceforge.net>,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: virtio-9p error
Date: Thu, 09 Sep 2010 17:47:43 -0700	[thread overview]
Message-ID: <4C89802F.5020003@linux.vnet.ibm.com> (raw)
In-Reply-To: <4C866B4A.6070204@linux.vnet.ibm.com>

On 9/7/2010 9:41 AM, Venkateswararao Jujjuri (JV) wrote:
> Bruno Cesar Ribas wrote:
>> On Thu, Aug 26, 2010 at 09:44:32AM -0700, Venkateswararao Jujjuri (JV) wrote:
>>> Bruno Cesar Ribas wrote:
>>>> Hi,
>>>>
>>> [snip]
>>> This quick test is with QEMU patches that are on mailing lists but not merged
>>> into mainline.
>>> Being said that, I don't think they really affect this.
>>
>> is there any work to bring these patches to mainline?
>>
>> There's no imprevement on virtio-9p in qemu since my first email.
>
> I sent a new revision on Thursday. I am expecting that they will go in anytime.
>
> Last time I talked to Anthony, he is planning on taking these patches soon.

Hello, now the patches are on the mainline tree. Please try them out.

Thanks,
JV

>
> Thanks,
> JV
>
>>
>>>> [snip]
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2010-09-10  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26  4:39 virtio-9p error Bruno Cesar Ribas
2010-08-26 16:44 ` Venkateswararao Jujjuri (JV)
2010-09-04  4:01   ` Bruno Cesar Ribas
2010-09-07 16:41     ` Venkateswararao Jujjuri (JV)
2010-09-10  0:47       ` Venkateswararao Jujjuri (JV) [this message]

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=4C89802F.5020003@linux.vnet.ibm.com \
    --to=jvrao@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ribas@c3sl.ufpr.br \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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.