From: David Miller <davem@davemloft.net>
To: florian@openwrt.org
Cc: n0-1@freewrt.org, netdev@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] korina: fix loop back of receive descriptors
Date: Mon, 19 Jan 2009 16:23:40 -0800 (PST) [thread overview]
Message-ID: <20090119.162340.81953132.davem@davemloft.net> (raw)
In-Reply-To: <200901192207.32649.florian@openwrt.org>
From: Florian Fainelli <florian@openwrt.org>
Date: Mon, 19 Jan 2009 22:07:30 +0100
> Le Thursday 15 January 2009 23:29:55 Phil Sutter, vous avez écrit :
> > After the last loop iteration, i has the value RC32434_NUM_RDS and
> > therefore leads to an index overflow when used afterwards to address the
> > last element. This is yet another another bug introduced when rewriting
> > parts of the driver for upstream preparation, as the original driver
> > used 'RC32434_NUM_RDS - 1' instead.
> >
> > Signed-off-by: Phil Sutter <n0-1@freewrt.org>
>
> Acked-by: Florian Fainelli <florian@openwrt.org>
Applied.
prev parent reply other threads:[~2009-01-20 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 22:29 [PATCH] korina: fix loop back of receive descriptors Phil Sutter
2009-01-19 21:07 ` Florian Fainelli
2009-01-20 0:23 ` 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=20090119.162340.81953132.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=jeff@garzik.org \
--cc=n0-1@freewrt.org \
--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).