From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
Alex Ng <alexng@microsoft.com>
Subject: Re: [PATCH 1/2] Drivers: hv: utils: Continue to poll VSS channel after handling requests.
Date: Wed, 31 Aug 2016 12:45:53 +0200 [thread overview]
Message-ID: <20160831104553.GA28851@kroah.com> (raw)
In-Reply-To: <1471544215-13999-1-git-send-email-kys@exchange.microsoft.com>
On Thu, Aug 18, 2016 at 11:16:54AM -0700, kys@exchange.microsoft.com wrote:
> From: Alex Ng <alexng@microsoft.com>
>
> Multiple VSS_OP_HOT_BACKUP requests may arrive in quick succession, even
> though the host only signals once. The driver wass handling the first
> request while ignoring the others in the ring buffer. We should poll the
> VSS channel after handling a request to continue processing other requests.
>
> Signed-off-by: Alex Ng <alexng@microsoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/hv/hv_snapshot.c | 89 +++++++++++++++++++++------------------------
> 1 files changed, 42 insertions(+), 47 deletions(-)
Also doesn't apply, please fix up and resend this series.
thanks,
greg k-h
next prev parent reply other threads:[~2016-08-31 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 18:16 [PATCH 0/2] Drivers: hv: util: Some fixes to the backup driver kys
2016-08-18 18:16 ` [PATCH 1/2] Drivers: hv: utils: Continue to poll VSS channel after handling requests kys
2016-08-18 18:16 ` [PATCH 2/2] Drivers: hv: utils: Check VSS daemon is listening before a hot backup kys
2016-08-31 10:45 ` Greg KH [this message]
2016-08-31 17:57 ` [PATCH 1/2] Drivers: hv: utils: Continue to poll VSS channel after handling requests KY Srinivasan
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=20160831104553.GA28851@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexng@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@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).