From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH RESEND 0/5] Tools: hv: fix compiler warnings and do minor cleanup
Date: Fri, 9 Jan 2015 22:18:10 -0800 [thread overview]
Message-ID: <1420870690-2223-1-git-send-email-kys@microsoft.com> (raw)
When someone does 'make' in tools/hv/ issues appear:
- hv_fcopy_daemon is not being built;
- lots of compiler warnings.
This is just a cleanup. Compile-tested by myself on top of linux-next/master.
Piggyback this series and send "[PATCH 5/5] Tools: hv: do not add redundant '/'
in hv_start_fcopy()"
Vitaly Kuznetsov (5):
Tools: hv: add mising fcopyd to the Makefile
Tools: hv: remove unused bytes_written from kvp_update_file()
Tools: hv: address compiler warnings for hv_kvp_daemon.c
Tools: hv: address compiler warnings for hv_fcopy_daemon.c
Tools: hv: do not add redundant '/' in hv_start_fcopy()
tools/hv/Makefile | 4 ++--
tools/hv/hv_fcopy_daemon.c | 10 ++--------
tools/hv/hv_kvp_daemon.c | 29 +++++++++++++----------------
3 files changed, 17 insertions(+), 26 deletions(-)
--
1.7.4.1
next reply other threads:[~2015-01-10 5:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 6:18 K. Y. Srinivasan [this message]
2015-01-10 6:18 ` [PATCH RESEND 1/5] Tools: hv: add mising fcopyd to the Makefile K. Y. Srinivasan
2015-01-10 6:18 ` [PATCH RESEND 2/5] Tools: hv: remove unused bytes_written from kvp_update_file() K. Y. Srinivasan
2015-01-10 6:18 ` [PATCH RESEND 3/5] Tools: hv: address compiler warnings for hv_kvp_daemon.c K. Y. Srinivasan
2015-01-10 6:18 ` [PATCH RESEND 4/5] Tools: hv: address compiler warnings for hv_fcopy_daemon.c K. Y. Srinivasan
2015-01-10 6:18 ` [PATCH RESEND 5/5] Tools: hv: do not add redundant '/' in hv_start_fcopy() K. Y. Srinivasan
2015-01-25 13:34 ` [PATCH RESEND 1/5] Tools: hv: add mising fcopyd to the Makefile Greg KH
2015-01-26 10:07 ` Vitaly Kuznetsov
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=1420870690-2223-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--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 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.