From: Greg KH <gregkh@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
virtualization@lists.osdl.org,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH]: Staging: hv: Cleanup vmalloc calls
Date: Fri, 11 Feb 2011 14:53:31 -0800 [thread overview]
Message-ID: <20110211225331.GA32412@suse.de> (raw)
In-Reply-To: <1297464525-23254-1-git-send-email-kys@microsoft.com>
On Fri, Feb 11, 2011 at 02:48:45PM -0800, K. Y. Srinivasan wrote:
> The subject says it all. There is no need to
> specify different page protection bits based
> on the architecture.
Wonderful, thanks for doing this. I'll queue it up after your previous
patches sometime next week.
thanks,
greg k-h
prev parent reply other threads:[~2011-02-11 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 22:48 [PATCH]: Staging: hv: Cleanup vmalloc calls K. Y. Srinivasan
2011-02-11 22:53 ` Greg KH [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=20110211225331.GA32412@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=hjanssen@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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).