From: Amit Shah <amit.shah@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: sjur@brendeland.net, "Michael S. Tsirkin" <mst@redhat.com>,
linus.walleij@linaro.org, masami.hiramatsu.pt@hitachi.com,
ohad@wizery.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Sjur Brændeland" <sjur.brandeland@stericsson.com>
Subject: Re: [[PATCH v9 3/3] 1/1] virtio_console: Remove buffers from out_vq at port removal
Date: Mon, 10 Dec 2012 11:24:01 +0530 [thread overview]
Message-ID: <20121210055401.GA17187@amit.redhat.com> (raw)
In-Reply-To: <87ip96id3a.fsf@rustcorp.com.au>
On (Fri) 16 Nov 2012 [11:22:09], Rusty Russell wrote:
> Amit Shah <amit.shah@redhat.com> writes:
> > From: Sjur Brændeland <sjur.brandeland@stericsson.com>
> >
> > Remove buffers from the out-queue when a port is removed. Rproc_serial
> > communicates with remote processors that may crash and leave buffers in
> > the out-queue. The virtio serial ports may have buffers in the out-queue
> > as well, e.g. for non-blocking ports and the host didn't consume them
> > yet.
> >
> > [Amit: Remove WARN_ON for generic ports case.]
> >
> > Signed-off-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
> > Signed-off-by: Amit Shah <amit.shah@redhat.com>
>
> I already have this in my pending queue; I've promoted it to my
> virtio-next branch now.
Rusty, I still see this series in your pending queue, not in
virtio-next. Did anything change in the meantime?
Amit
next prev parent reply other threads:[~2012-12-10 5:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 9:17 [[PATCH v9 3/3] 1/1] virtio_console: Remove buffers from out_vq at port removal Amit Shah
2012-11-16 0:52 ` Rusty Russell
2012-12-10 5:54 ` Amit Shah [this message]
2012-12-10 23:09 ` Rusty Russell
2012-12-11 4:10 ` Amit Shah
2012-12-12 0:01 ` Rusty Russell
2012-12-12 12:12 ` Amit Shah
2012-12-12 12:31 ` Sjur BRENDELAND
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=20121210055401.GA17187@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mst@redhat.com \
--cc=ohad@wizery.com \
--cc=rusty@rustcorp.com.au \
--cc=sjur.brandeland@stericsson.com \
--cc=sjur@brendeland.net \
--cc=virtualization@lists.linux-foundation.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).