From: David Brownell <david-b@pacbell.net>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] rndis_host: pass buffer length to rndis_command
Date: Wed, 18 Jun 2008 10:09:10 -0700 [thread overview]
Message-ID: <200806181009.10193.david-b@pacbell.net> (raw)
In-Reply-To: <20080618124011.11920.98218.stgit@fate.lan>
On Wednesday 18 June 2008, Jussi Kivilinna wrote:
> Pass buffer length to rndis_command so that rndis_command can read full
> response buffer from device instead of max CONTROL_BUFFER_SIZE bytes.
That is: allow rndis_wlan to get responses *bigger* than that size,
while preserving the requirement that the host must always be ready
to receive that many bytes.
> Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Acked-by: David Brownell <dbrownell@users.sourceforge.net>
next prev parent reply other threads:[~2008-06-18 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 12:40 [PATCH net-next] rndis_host: pass buffer length to rndis_command Jussi Kivilinna
2008-06-18 17:09 ` David Brownell [this message]
2008-06-18 22:04 ` Jussi Kivilinna
2008-06-27 6:09 ` Jeff Garzik
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=200806181009.10193.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=jussi.kivilinna@mbnet.fi \
--cc=netdev@vger.kernel.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).