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 0000/0003] Staging: hv: Driver cleanup
Date: Sun, 18 Sep 2011 10:30:53 -0700 [thread overview]
Message-ID: <1316367053-700-1-git-send-email-kys@microsoft.com> (raw)
Address Greg's VmBus audit comments:
1) Make the util driver conform to the Linux Driver Model.
Regards,
K. Y
next reply other threads:[~2011-09-18 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 17:30 K. Y. Srinivasan [this message]
2011-09-18 17:31 ` [PATCH 1/3] Staging: hv: util: Perform some service specific init/deinit in probe/remove K. Y. Srinivasan
2011-09-18 17:31 ` [PATCH 2/3] Staging: hv: util: Properly handle util services in the util driver K. Y. Srinivasan
2011-09-18 17:31 ` [PATCH 3/3] Staging: hv: vmbus: Get rid of hv_cb_utils[] and other unneeded code K. Y. Srinivasan
2011-09-18 17:53 ` [PATCH 1/3] Staging: hv: util: Perform some service specific init/deinit in probe/remove Joe Perches
2011-09-18 22:26 ` 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=1316367053-700-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;
as well as URLs for NNTP newsgroup(s).