Re: [RFC 02/16] KVM: selftests: add hooks for managing encrypted guest memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13/10/21 17:07, Michael Roth wrote:

For readability, it's probably better to adopt a standard naming convention
for structures, members and  functions ?  For example,

         encrypted_phy_pages    ->     enc_phy_pages

         struct vm_memcrypt  {    ->    struct vm_mem_enc {

         struct vm_memcrypt memcrypt    ->    struct vm_mem_enc  mem_enc

         vm_get_encrypted_phy_pages()    -> vm_get_enc_phy_pages



Makes sense, I will use this naming convention for the next spin.

And again I liked yours more. :)

Paolo




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux