From: David Miller <davem@davemloft.net>
To: figo1802@gmail.com
Cc: zealcook@gmail.com, netdev@vger.kernel.org, ben@simtec.co.uk
Subject: Re: [PATCH 2/2 v2] KS8695: fix ks8695_rx() unreasonable action.
Date: Mon, 16 Nov 2009 23:52:00 -0800 (PST) [thread overview]
Message-ID: <20091116.235200.210617103.davem@davemloft.net> (raw)
In-Reply-To: <1258046194.1931.18.camel@myhost>
From: "Figo.zhang" <figo1802@gmail.com>
Date: Fri, 13 Nov 2009 01:16:34 +0800
> On Mon, 2009-11-16 at 22:58 +0800, zeal wrote:
>> From: zeal <zealcook@gmail.com>
>>
>> ks8695_rx() will call refill_buffers() for every incoming packet.
>> Its not necessary. We just need do it after finishing receiving thing.
>> And the 'RX dma engine' is in the same situation.
>> This blocks our user space application. The following patch may fix it.
>>
>
> yes, it is right.
>
> Best,
> Figo.zhang
>
>> Signed-off-by: zeal <zealcook@gmail.com>
Patch applied.
prev parent reply other threads:[~2009-11-17 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1258383490-13341-1-git-send-email-zeal>
2009-11-16 14:58 ` [PATCH 2/2 v2] KS8695: fix ks8695_rx() unreasonable action zeal
2009-11-12 17:16 ` Figo.zhang
2009-11-17 7:52 ` 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=20091116.235200.210617103.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben@simtec.co.uk \
--cc=figo1802@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zealcook@gmail.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).