From: Greg KH <gregkh@suse.de>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: devel@linuxdriverproject.org, virtualization@lists.osdl.org,
hjanssen@microsoft.com, linux-kernel@vger.kernel.org,
Haiyang Zhang <haiyangz@microsoft.com>,
Abhishek Kane <v-abkane@microsoft.com>
Subject: Re: [PATCH 2/8] staging: hv: Convert camel case struct fields in storvsc_api.h to lowercase
Date: Mon, 6 Dec 2010 18:02:23 -0800 [thread overview]
Message-ID: <20101207020223.GA25981@suse.de> (raw)
In-Reply-To: <4CFD24820200003000091628@novprvoes0310.provo.novell.com>
On Mon, Dec 06, 2010 at 05:59:30PM -0700, Ky Srinivasan wrote:
> Greg,
>
> My new KVP patches are ready to go. Should I wait for Hank's patches
> to be checked in before I send the KVP patches?
Hank's patches went in a few hours ago :)
thanks,
greg k-h
prev parent reply other threads:[~2010-12-07 2:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 20:26 [PATCH 1/8] staging: hv: Convert camel case struct fields in vstorage.h to lowercase Hank Janssen
2010-12-06 20:26 ` [PATCH 2/8] staging: hv: Convert camel case struct fields in storvsc_api.h " Hank Janssen
2010-12-06 20:26 ` [PATCH 3/8] staging: hv: Convert camel case functions " Hank Janssen
2010-12-06 20:26 ` [PATCH 4/8] staging: hv: Convert camel case struct fields in storvsc.c " Hank Janssen
2010-12-06 20:26 ` [PATCH 5/8] staging: hv: Convert camel case function names " Hank Janssen
2010-12-06 20:26 ` [PATCH 6/8] staging: hv: Convert camel case local variables " Hank Janssen
2010-12-06 20:26 ` [PATCH 7/8] staging: hv: Convert camel case function names in blkvsc.c " Hank Janssen
2010-12-06 20:26 ` [PATCH 8/8] staging: hv: Convert camel case local variables " Hank Janssen
2010-12-07 0:59 ` [PATCH 2/8] staging: hv: Convert camel case struct fields in storvsc_api.h " Ky Srinivasan
2010-12-07 2:02 ` Greg KH [this message]
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=20101207020223.GA25981@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=ksrinivasan@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=v-abkane@microsoft.com \
--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).