From: Jeff Garzik <jeff@garzik.org>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: csnook@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jareguero@telefonica.net,
atl1-devel@lists.sourceforge.net
Subject: Re: [PATCH] atl1: remove unnecessary crc inversion
Date: Wed, 28 Mar 2007 02:19:53 -0400 [thread overview]
Message-ID: <460A0909.8000607@garzik.org> (raw)
In-Reply-To: <20070328004349.GA2792@osprey.hogchain.net>
Jay Cliburn wrote:
> From: Jay Cliburn <jacliburn@bellsouth.net>
>
> The original vendor driver contained a private ether_crc_le() function
> that produced an inverted crc. When we changed to the kernel version of
> ether_crc_le(), we neglected to undo the inversion. Let's do it now.
> Discovered by and patch proffered by Jose Alberto Reguero.
>
> Signed-off-by: Jose Alberto Reguero <jareguero@telefonica.net>
> Signed-off-by: Jay Cliburn <jacliburn@bellsouth.net>
applied to #upstream-fixes
prev parent reply other threads:[~2007-03-28 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 0:43 [PATCH] atl1: remove unnecessary crc inversion Jay Cliburn
2007-03-28 6:19 ` Jeff Garzik [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=460A0909.8000607@garzik.org \
--to=jeff@garzik.org \
--cc=atl1-devel@lists.sourceforge.net \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=jareguero@telefonica.net \
--cc=linux-kernel@vger.kernel.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).