From: David Miller <davem@davemloft.net>
To: petkan@nucleusys.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] drivers: net: usb: pegasus: bug fixing and cleanup
Date: Mon, 29 Apr 2013 14:04:24 -0400 (EDT) [thread overview]
Message-ID: <20130429.140424.2195591601359157776.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1304261008410.3772@fry.nucleusys.com>
From: Petko Manolov <petkan@nucleusys.com>
Date: Fri, 26 Apr 2013 10:13:41 +0300 (EEST)
> From: Petko Manolov <petkan@nucleusys.com>
>
> This series of patches is fixing a bug related to multiple control URB
> submissions (noted by Sarah Sharp), optimizes read and write_mii_word
> routines and removes socket buffer pool used in the receive path.
>
> Signed-off-by: Petko Manolov <petkan@nucleusys.com>
Series applied, thanks.
prev parent reply other threads:[~2013-04-29 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 7:13 [PATCH 0/3] drivers: net: usb: pegasus: bug fixing and cleanup Petko Manolov
2013-04-26 8:44 ` Petko Manolov
2013-04-29 18:04 ` 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=20130429.140424.2195591601359157776.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.com \
/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).