From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@suse.de, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, virtualization@lists.osdl.org
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 0/2] Staging: hv: Fixup Phase II storage driver cleanup
Date: Wed, 6 Apr 2011 11:24:46 -0700 [thread overview]
Message-ID: <1302114286-2127-1-git-send-email-kys@microsoft.com> (raw)
This fixes a couple of bugs that was introduced in the patch-set titled:
Staging: hv: Cleanup storage drivers phase II.
A corrected version of this patch-set was sent out earlier, however
the earlier (buggy) version of this patch-set was already applied.
This patch set fixes this problem..
Regards,
K. Y
next reply other threads:[~2011-04-06 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 18:24 K. Y. Srinivasan [this message]
2011-04-06 18:25 ` [PATCH 1/2] Staging: hv: Properly capture the error state K. Y. Srinivasan
2011-04-06 18:25 ` [PATCH 2/2] Staging: hv: Zero out the request structure on allocation K. Y. 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=1302114286-2127-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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