From: David Miller <davem@davemloft.net>
To: haiyangz@microsoft.com
Cc: netdev@vger.kernel.org, kys@microsoft.com, olaf@aepfle.de,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org
Subject: Re: [PATCH net-next,1/6] hyperv: Fix the max_xfer_size in RNDIS initialization
Date: Tue, 02 Oct 2012 14:40:07 -0400 (EDT) [thread overview]
Message-ID: <20121002.144007.686391086427399732.davem@davemloft.net> (raw)
In-Reply-To: <1349191824-14001-1-git-send-email-haiyangz@microsoft.com>
From: Haiyang Zhang <haiyangz@microsoft.com>
Date: Tue, 2 Oct 2012 08:30:19 -0700
> According to RNDIS specs, Windows sets this size to
> 0x4000. I use the same value here.
>
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> Reviewed-by: K. Y. Srinivasan <kys@microsoft.com>
Applied.
prev parent reply other threads:[~2012-10-02 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 15:30 [PATCH net-next,1/6] hyperv: Fix the max_xfer_size in RNDIS initialization Haiyang Zhang
2012-10-02 15:30 ` [PATCH net-next,2/6] hyperv: Fix the missing return value in rndis_filter_set_packet_filter() Haiyang Zhang
2012-10-02 18:42 ` David Miller
2012-10-02 15:30 ` [PATCH net-next, 3/6] hyperv: Fix page buffer handling in rndis_filter_send_request() Haiyang Zhang
2012-10-02 18:42 ` [PATCH net-next,3/6] " David Miller
2012-10-02 15:30 ` [PATCH net-next,4/6] hyperv: Remove extra allocated space for recv_pkt_list elements Haiyang Zhang
2012-10-02 18:42 ` David Miller
2012-10-02 15:30 ` [PATCH net-next,5/6] hyperv: Report actual status in receive completion packet Haiyang Zhang
2012-10-02 18:42 ` David Miller
2012-10-02 15:30 ` [PATCH net-next,6/6] hyperv: Add buffer for extended info after the RNDIS response message Haiyang Zhang
2012-10-02 18:42 ` David Miller
2012-10-02 18:40 ` David Miller [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=20121002.144007.686391086427399732.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).