On Fri, Dec 01, 2023 at 03:24:48PM -0800, Alexey Makhalov wrote: > Introducing vmware_hypercall family of functions as a common > implementation to be used by the VMware guest code and virtual > device drivers in architecture independent manner. > > By analogy with KVM hypercall API, vmware_hypercallX and > vmware_hypercall_hb_{out,in} set of functions was added to > achieve that. Architecture specific implementation should be > hidden inside. Pls read section "2) Describe your changes" in Documentation/process/submitting-patches.rst for more details on how to formulate your commit messages. Also, see section "Changelog" in Documentation/process/maintainer-tip.rst More specifically: "Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour." Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette