All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Netdev <netdev@oss.sgi.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	stable@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCHES] 2.6.x net driver oops fixes
Date: Thu, 10 Mar 2005 13:35:54 -0800	[thread overview]
Message-ID: <20050310213554.GA21061@kroah.com> (raw)
In-Reply-To: <20050310203112.GA20337@kroah.com>

On Thu, Mar 10, 2005 at 12:31:12PM -0800, Greg KH wrote:
> On Thu, Mar 10, 2005 at 12:25:48PM -0800, 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 pci_name() portion of this patch is not necessary for the -stable
> tree.  Care to remove it?

Oh nevermind, I was completly wrong, it's fine.

greg k-h

      reply	other threads:[~2005-03-10 21:36 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
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 [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=20050310213554.GA21061@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --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 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.