From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Include the limit on the number of pfns we can handle
Date: Thu, 6 Mar 2014 22:48:49 -0800 [thread overview]
Message-ID: <20140307064849.GB20065@kroah.com> (raw)
In-Reply-To: <1394176508-1439-1-git-send-email-kys@microsoft.com>
On Thu, Mar 06, 2014 at 11:15:08PM -0800, K. Y. Srinivasan wrote:
> Increase the maximum number of pfns we can handle is a single vmbus packet.
Is that a correct sentance?
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> include/linux/hyperv.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
> index 330ec44..ab7359f 100644
> --- a/include/linux/hyperv.h
> +++ b/include/linux/hyperv.h
> @@ -37,7 +37,7 @@
> #include <linux/mod_devicetable.h>
>
>
> -#define MAX_PAGE_BUFFER_COUNT 19
> +#define MAX_PAGE_BUFFER_COUNT 32
What is the problem if this number isn't changed?
Again, I'm going to have to ask you, what kernel is this for?
Please remember this when sending patches that look like they might be
fixing a bug, you don't want me to guess, as my "guess" usually is
"delete the patch".
greg k-h
next prev parent reply other threads:[~2014-03-07 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 7:15 K. Y. Srinivasan
2014-03-07 6:48 ` Greg KH [this message]
2014-03-07 6:58 ` KY Srinivasan
2014-03-07 8:16 ` Dan Carpenter
2014-03-07 9:07 ` KY Srinivasan
2014-03-07 9:20 ` Dan Carpenter
2014-03-07 15:50 ` KY Srinivasan
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=20140307064849.GB20065@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
Powered by JetHome