netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Chris Wright <chrisw@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>, Netdev <netdev@oss.sgi.com>,
	stable@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>,
	Roger Luethi <rl@hellgate.ch>
Subject: Re: [stable] [BK PATCHES] 2.6.x net driver oops fixes
Date: Thu, 10 Mar 2005 13:39:17 -0800	[thread overview]
Message-ID: <20050310213917.GW5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <4230AE24.602@pobox.com>

* Jeff Garzik (jgarzik@pobox.com) wrote:
> Chris Wright wrote:
> >* Jeff Garzik (jgarzik@pobox.com) wrote:
> >
> >
> >>This will update the following files:
> >>
> >>drivers/net/sis900.c    |   41 +++++++++++++++++++++--------------------
> >>drivers/net/via-rhine.c |    3 +++
> >
> >
> >The via-rhine fix is already in the stable queue.  But the sis900 oops
> >fix does not apply to the stable tree.  It relies on a few intermediate
> >patches.  Appears to still be an issue for the older version which is in
> >2.6.11.  Here's a stab at a backport.  Would you like to review/validate
> >or drop this one?
> 
> The backport looks correct to me, though it would be nice to get a 
> via-rhine owner to ACK the patch before it goes in...

OK, thanks.  ITYM sis900 maintainer, is that still Ollie Lho as listed in
MAINTAINERS (that's looking old)?

thanks,
-chris

  reply	other threads:[~2005-03-10 21:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 20:17 [BK PATCHES] 2.6.x net driver oops fixes Jeff Garzik
2005-03-10 20:25 ` [stable] " Chris Wright
2005-03-10 20:29   ` Jeff Garzik
2005-03-10 21:39     ` Chris Wright [this message]
2005-03-11 19:29       ` Daniele Venzano
2005-03-11 19:32         ` Jeff Garzik
2005-03-11 19:36         ` Chris Wright
2005-03-10 20:31   ` Greg KH
2005-03-10 21:35     ` Greg KH

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=20050310213917.GW5389@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=rl@hellgate.ch \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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).