From: David Miller <davem@davemloft.net>
To: manuel.lauss@googlemail.com
Cc: roel.kluin@gmail.com, netdev@vger.kernel.org,
akpm@linux-foundation.org, manuel.lauss@gmail.com
Subject: Re: [PATCH] au1000_eth: Duplicate test of RX_OVERLEN bit in update_rx_stats()
Date: Wed, 07 Oct 2009 03:44:54 -0700 (PDT) [thread overview]
Message-ID: <20091007.034454.156559196.davem@davemloft.net> (raw)
In-Reply-To: <f861ec6f0910061253g28743e80r2db772aa7101f098@mail.gmail.com>
From: Manuel Lauss <manuel.lauss@googlemail.com>
Date: Tue, 6 Oct 2009 21:53:50 +0200
> On Tue, Oct 6, 2009 at 9:54 PM, Roel Kluin <roel.kluin@gmail.com> wrote:
>> in update_rx_stats() the RX_OVERLEN bit is set twice, replace it by RX_RUNT.
>> in au1000_rx() the RX_MISSED_FRAME bit was tested a few lines earlier already
>>
>> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
...
>
> Yeah, looks right.
>
> Acked-by: Manuel Lauss <manuel.lauss@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2009-10-07 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 19:54 [PATCH] au1000_eth: Duplicate test of RX_OVERLEN bit in update_rx_stats() Roel Kluin
2009-10-06 19:53 ` Manuel Lauss
2009-10-07 10:44 ` 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=20091007.034454.156559196.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=manuel.lauss@gmail.com \
--cc=manuel.lauss@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@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