linux-kernel - Re: [PATCH 2/2] Staging: hv: General maintenance of TODO file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100212001159.GC13769@brick.ozlabs.ibm.com>
Date:	Fri, 12 Feb 2010 11:11:59 +1100
From:	Paul Mackerras <paulus@...ba.org>
To:	Hank Janssen <hjanssen@...rosoft.com>
Cc:	Greg KH <gregkh@...e.de>,
	"'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 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.
--
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/