From: Chuck Ebbert <cebbert@redhat.com>
To: Herbert Xu <herbert.xu@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Auke Kok <auke-jan.h.kok@intel.com>,
stable@vger.kernel.org, greg@suse.de,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
davej@redhat.com
Subject: Re: [PATCH] e1000: Don't enable polling in open() (was: e1000: assertion hit in e1000_clean(), kernel 2.6.21.1)
Date: Tue, 22 May 2007 12:56:06 -0400 [thread overview]
Message-ID: <465320A6.80706@redhat.com> (raw)
In-Reply-To: <20070522010137.GC8130@gondor.apana.org.au>
Herbert Xu wrote:
> On Mon, May 21, 2007 at 07:42:39PM -0400, Jeff Garzik wrote:
>> applied, though as a poster (DaveJ?) noted, I'm not sure it completely
>> fixes the bug
>
> It should fix the problem completely in 2.6.22. For 2.6.21, we need
> a different fix because e1000_open is directly calling e1000_up.
>
Is there going to be a 2.6.21-stable fix for this?
Fedora is going to backport a big patchset but that won't work
for -stable.
next prev parent reply other threads:[~2007-05-22 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 21:51 [PATCH] e1000: Don't enable polling in open() (was: e1000: assertion hit in e1000_clean(), kernel 2.6.21.1) Auke Kok
2007-05-21 22:16 ` Dave Jones
2007-05-22 0:49 ` Herbert Xu
2007-05-22 0:58 ` Kok, Auke
2007-05-22 1:22 ` Dave Jones
2007-05-21 23:42 ` Jeff Garzik
2007-05-22 0:04 ` Kok, Auke
2007-05-22 1:01 ` Herbert Xu
2007-05-22 16:56 ` Chuck Ebbert [this message]
2007-05-22 17:02 ` Kok, Auke
2007-05-23 10:47 ` Herbert Xu
2007-05-23 23:34 ` Chris Wright
2007-05-23 23:38 ` Kok, Auke
2007-05-24 1:29 ` Herbert Xu
2007-05-24 4:31 ` Chris Wright
2007-05-24 1:29 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2007-05-21 15:32 Auke Kok
2007-05-21 21:26 ` Herbert Xu
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=465320A6.80706@redhat.com \
--to=cebbert@redhat.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davej@redhat.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greg@suse.de \
--cc=herbert.xu@redhat.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.