From: Jeff Garzik <jeff@garzik.org>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: netdev@vger.kernel.org, dbrownell@users.sourceforge.net
Subject: Re: [PATCH net-next] rndis_host: pass buffer length to rndis_command
Date: Fri, 27 Jun 2008 02:09:25 -0400 [thread overview]
Message-ID: <48648415.9090602@garzik.org> (raw)
In-Reply-To: <20080618124011.11920.98218.stgit@fate.lan>
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.
>
> Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
> ---
>
> drivers/net/usb/rndis_host.c | 14 +++++++-------
> drivers/net/wireless/rndis_wlan.c | 4 ++--
> include/linux/usb/rndis_host.h | 3 ++-
> 3 files changed, 11 insertions(+), 10 deletions(-)
applied
prev parent reply other threads:[~2008-06-27 6: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
2008-06-18 22:04 ` Jussi Kivilinna
2008-06-27 6:09 ` Jeff Garzik [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=48648415.9090602@garzik.org \
--to=jeff@garzik.org \
--cc=dbrownell@users.sourceforge.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).