netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Fry <brazilnut@us.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: murrayma@citi.umich.edu, netdev@vger.kernel.org, strel@ioc.ac.ru
Subject: Re: [PATCH] pcnet32: break in 2.6.18-rc1 identified (corrected)
Date: Wed, 9 Aug 2006 08:35:01 -0700	[thread overview]
Message-ID: <20060809153501.GA30459@us.ibm.com> (raw)
In-Reply-To: <44D95E1E.9010403@garzik.org>

On Wed, Aug 09, 2006 at 12:01:34AM -0400, Jeff Garzik wrote:
> Don Fry wrote:
> >I noticed this morning that I had the polarity wrong in my patch
> >yesterday for older chips in the pcnet32_suspend routine.  Here is the
> >correct patch to test.
> >
> >>A change I made for 2.6.17 and another for 2.6.18 do not work on older
> >>pcnet32 chips which I do not have access to.  Please test this patch if
> >>you have access to a 79C970, 79C974, or 79C965 (VLB) version of the
> >>pcnet32 and let me know if it solves any problems.  I have tested with a
> >>79C970A, 79C971, 79C972, 79C973, 79C975, 79C976, and 79C978 and the
> >>changes work as expected.
> 
> Did testing succeed?
> 

I have not heard anything about testing results yet.  I have tested
successfully with the hardware I have, but there are at least three
variants of the chip that I have not been able to find.  "It should
work" are the famous last words of most programmers ;-(.  I received an
email from Martin on Saturday that he had been traveling and would get
back to me.  I believe that the patch will resolve the issue with older
cards.  The patch is no worse than what is in 2.6.18-rc4 today, but
removing the offending patch is also an option.

The patch also addresses an issue raised by Yuri Strelenko that the
changes in 2.6.17 caused his 79C970 to stop working.  I have sent him a
patch as well, but have heard nothing from him.  Those changes I am much
more positive about, but I would like confirmation that I have not
broken something else.

When I have some positive results, I will add the signed-off-by line and
resubmit the patch or ask for the old patch to be removed.  When does
the patch need to be submitted in order to be included in 2.6.18?

> signed-off-by?
> 
> 	Jeff
-- 
Don Fry
brazilnut@us.ibm.com

  reply	other threads:[~2006-08-09 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 16:26 [PATCH] pcnet32: break in 2.6.18-rc1 identified (corrected) Don Fry
2006-08-09  4:01 ` Jeff Garzik
2006-08-09 15:35   ` Don Fry [this message]
2006-08-09 16:12     ` Jeff Garzik

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=20060809153501.GA30459@us.ibm.com \
    --to=brazilnut@us.ibm.com \
    --cc=jeff@garzik.org \
    --cc=murrayma@citi.umich.edu \
    --cc=netdev@vger.kernel.org \
    --cc=strel@ioc.ac.ru \
    /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).