From: Jeff Garzik <jgarzik@pobox.com>
To: Philip Craig <philipc@snapgear.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] 8139cp: fix eeprom read command length
Date: Tue, 20 Jun 2006 04:52:10 -0400 [thread overview]
Message-ID: <4497B73A.4080804@pobox.com> (raw)
In-Reply-To: <448FAFF5.7040701@snapgear.com>
Philip Craig wrote:
> The read command for the 93C46/93C56 EEPROMS should be 3 bits plus
> the address. This doesn't appear to affect the operation of the
> read command, but similar errors for write commands do cause failures.
>
> Signed-off-by: Philip Craig <philipc@snapgear.com>
ACK patches 1-2, but patch appears corrupted:
[jgarzik@pretzel netdev-2.6]$ git-applymbox /g/tmp/mbox ~/info/signoff.txt
2 patch(es) to process.
Applying '8139cp: fix eeprom read command length'
fatal: corrupt patch at line 7
next prev parent reply other threads:[~2006-06-20 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 6:43 [PATCH 1/2] 8139cp: fix eeprom read command length Philip Craig
2006-06-20 8:52 ` Jeff Garzik [this message]
2006-06-21 1:33 ` [PATCH 1/2 resend] " Philip Craig
2006-06-23 3:20 ` Jeff Garzik
2006-06-21 1:33 ` [PATCH 2/2 resend] 8139cp: add ethtool eeprom support Philip Craig
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=4497B73A.4080804@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=philipc@snapgear.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).