linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishnu DASA <vdasa@vmware.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"virtualization@lists.linux-foundation.org" 
	<virtualization@lists.linux-foundation.org>,
	Pv-drivers <Pv-drivers@vmware.com>
Subject: Re: [PATCH] VMCI: Support upto 64-bit PPNs
Date: Thu, 21 Feb 2019 19:26:29 +0000	[thread overview]
Message-ID: <8C694A7E-488C-42A9-83F8-AA4FB4E57A5A@vmware.com> (raw)
In-Reply-To: <20190216195253.GB11061@kroah.com>

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@linuxfoundation.org" <gregkh@linuxfoundation.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()?
    
    


  reply	other threads:[~2019-02-21 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 16:32 [PATCH] VMCI: Support upto 64-bit PPNs Vishnu DASA
2019-02-16 19:52 ` gregkh
2019-02-21 19:26   ` Vishnu DASA [this message]
2019-02-21 19:42     ` gregkh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8C694A7E-488C-42A9-83F8-AA4FB4E57A5A@vmware.com \
    --to=vdasa@vmware.com \
    --cc=Pv-drivers@vmware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).