All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: zanghongyong@huawei.com
Cc: kvm@vger.kernel.org, rusty@rustcorp.com.au, aliguori@us.ibm.com,
	xiaowei.yang@huawei.com, hanweidong@huawei.com,
	wusongwei@huawei.com, jiangningyu@huawei.com, asias@redhat.com,
	Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/2] virtio-serial: set up vqs on demand
Date: Mon, 8 Apr 2013 13:21:42 +0530	[thread overview]
Message-ID: <20130408075142.GA18572@amit.redhat.com> (raw)
In-Reply-To: <1326331207-10339-1-git-send-email-zanghongyong@huawei.com>

On (Thu) 12 Jan 2012 [09:20:05], zanghongyong@huawei.com wrote:
> From: Hongyong Zang <zanghongyong@huawei.com>
> 
> Virtio-serial set up (max_ports+1)*2 vqs when device probes, but may not all 
> io_ports are used.
> These patches create vqs of port0 and control port when probing the device, then 
> create io-vqs when called add_port().

Hi,

Can you resurrect this series?  I think last time we were waiting for
a v2, but looks like it got lost.

Let me know if you're not interested anymore, and I can do something
about it.

Thanks,

		Amit

      parent reply	other threads:[~2013-04-08  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  1:20 [PATCH 0/2] virtio-serial: set up vqs on demand zanghongyong
2012-01-12  1:20 ` [PATCH 1/2] virtio-pci: add setup_vqs flag in vp_try_to_find_vqs zanghongyong
2012-02-01  8:14   ` Amit Shah
2012-02-01  9:54   ` Michael S. Tsirkin
2012-02-03  3:56     ` Rusty Russell
2012-01-12  1:20 ` [PATCH 2/2] virtio-serial: setup_port_vq when adding port zanghongyong
2012-02-01  8:12   ` Amit Shah
2012-02-01  9:32     ` Zang Hongyong
2012-02-01  9:40 ` [PATCH 0/2] virtio-serial: set up vqs on demand Michael S. Tsirkin
2013-04-08  7:51 ` Amit Shah [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=20130408075142.GA18572@amit.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=asias@redhat.com \
    --cc=hanweidong@huawei.com \
    --cc=jiangningyu@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wusongwei@huawei.com \
    --cc=xiaowei.yang@huawei.com \
    --cc=zanghongyong@huawei.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 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.