From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Vishnu DASA <vdasa@vmware.com>
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 20:42:19 +0100 [thread overview]
Message-ID: <20190221194219.GA2347@kroah.com> (raw)
In-Reply-To: <8C694A7E-488C-42A9-83F8-AA4FB4E57A5A@vmware.com>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Feb 21, 2019 at 07:26:29PM +0000, Vishnu DASA wrote:
> 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)?
Yes, that would be fine.
thanks,
greg k-h
prev parent reply other threads:[~2019-02-21 19:42 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
2019-02-21 19:42 ` gregkh [this message]
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=20190221194219.GA2347@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Pv-drivers@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vdasa@vmware.com \
--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).