[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8C694A7E-488C-42A9-83F8-AA4FB4E57A5A@vmware.com>
Date: Thu, 21 Feb 2019 19:26:29 +0000
From: Vishnu DASA <vdasa@...are.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Pv-drivers <Pv-drivers@...are.com>
Subject: Re: [PATCH] VMCI: Support upto 64-bit PPNs
Hi Greg,
Sounds like a good idea to use the BIT() macro but can I do that in a separate change to cover the entire file (and perhaps other vmci files too)?
Thanks,
Vishnu
On 2/16/19, 11:53 AM, "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org> wrote:
On Fri, Feb 15, 2019 at 04:32:47PM +0000, Vishnu DASA wrote:
> diff --git a/include/linux/vmw_vmci_defs.h b/include/linux/vmw_vmci_defs.h
> index b724ef7005de..eaa1e762bf06 100644
> --- a/include/linux/vmw_vmci_defs.h
> +++ b/include/linux/vmw_vmci_defs.h
> @@ -45,6 +45,7 @@
> #define VMCI_CAPS_GUESTCALL 0x2
> #define VMCI_CAPS_DATAGRAM 0x4
> #define VMCI_CAPS_NOTIFICATIONS 0x8
> +#define VMCI_CAPS_PPN64 0x10
BIT()?
Powered by blists - more mailing lists