public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org, tsbogend@alpha.franken.de,
	eli.carter@inet.com, alan@redhat.com
Subject: Re: [PATCH] pcnet32.c ARM support & AM79C973 improvements
Date: Thu, 18 Jan 2001 12:37:35 -0600	[thread overview]
Message-ID: <3A6737EF.C655ECCC@inet.com> (raw)
In-Reply-To: <3A671DD5.51B4DEE@inet.com>

Eli Carter wrote:
> Here is a patch that adds the following to the pcnet32.c driver:
[snip]
> - According to the Am79C973/Am79C975 docs from AMD, The collision bits
> are only valid if ENP is set, so I added a check for that.
[snip]
> @@ -1164,7 +1206,8 @@
>                     }
>  #endif
>                 } else {
> -                   if (status & 0x1800)
> +                   /* MORE and ONE are only valid if ENP is set */
> +                   if (status & 0x0040 && status & 0x1800)
>                         lp->stats.collisions++;
>                     lp->stats.tx_packets++;
>                 }

Argh.   That should read
+                   if (status & (1<<8) && status & 0x1800)
I'm tempted to change some of these magical numbers into #defines...
That would make it a bit easier to read, but have no functional
changes--would such a patch be accepted into the various trees?

Just my two bits.  ;)

Eli
--------------------. "To the systems programmer, users and applications
Eli Carter          | serve only to provide a test load."
eli.carter@inet.com `---------------------------------- (random fortune)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-18 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 16:46 [PATCH] pcnet32.c ARM support & AM79C973 improvements Eli Carter
2001-01-18 18:37 ` Eli Carter [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=3A6737EF.C655ECCC@inet.com \
    --to=eli.carter@inet.com \
    --cc=alan@redhat.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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