[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56212E8847D@TK5EX14MBXC118.redmond.corp.microsoft.com>
Date: Thu, 11 Feb 2010 23:46:48 +0000
From: Hank Janssen <hjanssen@...rosoft.com>
To: Greg KH <gregkh@...e.de>, Paul Mackerras <paulus@...ba.org>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: [PATCH 2/2] Staging: hv: General maintenance of TODO file
>> 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?
Thanks,
Hank.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists