From: Paul Mackerras <paulus@samba.org>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: Greg KH <gregkh@suse.de>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 2/2] Staging: hv: General maintenance of TODO file
Date: Fri, 12 Feb 2010 11:11:59 +1100 [thread overview]
Message-ID: <20100212001159.GC13769@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56212E8847D@TK5EX14MBXC118.redmond.corp.microsoft.com>
On Thu, Feb 11, 2010 at 11:46:48PM +0000, Hank Janssen wrote:
> >> On a side note, when this becomes mainstream, could you give it a more
> >> descriptive name than just "hv"? "Hv" already means at least two
> >> possible things to me -- "hypervisor" or "high volume" -- neither of
> >> which appear to be what this code is about.
> >
> >"hyperv" should be sufficient, right?
> >
> >thanks,
> >
> >greg k-h
>
> I was thinking of using that, but would that confuse it with hypervisor
> which is more of a general term? If the consensus is that it would not than
> I am in favor of changing it to hyperv.
>
> ms_hyperv would make it to long?
I don't believe "hyperv" is a generally-used abbreviation of
"hypervisor". You could do "ms_hyperv" if you like, but I wouldn't
regard the "ms_" prefix as essential.
Paul.
next prev parent reply other threads:[~2010-02-12 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8AFC7968D54FB448A30D8F38F259C56212E881A9@TK5EX14MBXC118.redmond.corp.microsoft.com>
2010-02-11 21:32 ` [PATCH 2/2] Staging: hv: General maintenance of TODO file Hank Janssen
2010-02-11 21:38 ` Greg KH
2010-02-11 22:22 ` Hank Janssen
2010-02-11 22:54 ` Greg KH
2010-02-11 23:04 ` Hank Janssen
2010-02-11 23:20 ` Paul Mackerras
2010-02-11 23:32 ` Greg KH
2010-02-11 23:46 ` Hank Janssen
2010-02-12 0:11 ` Paul Mackerras [this message]
2010-02-12 0:09 ` Paul Mackerras
2010-02-12 15:08 ` Haiyang Zhang
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=20100212001159.GC13769@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.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