From: Daniele Venzano <webvenza@libero.it>
To: Chris Wright <chrisw@osdl.org>
Cc: stable@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Netdev <netdev@oss.sgi.com>
Subject: Re: [stable] [BK PATCHES] 2.6.x net driver oops fixes
Date: Fri, 11 Mar 2005 20:29:50 +0100 [thread overview]
Message-ID: <c37a8fd17af92b648c6474904e0003c0@libero.it> (raw)
In-Reply-To: <20050310213917.GW5389@shell0.pdx.osdl.net>
On 10/mar/05, at 22:39, Chris Wright wrote:
> * 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)?
I have been acting maintainer for more than a year now, and I'm
completely fine with the patch.
A lot of time ago (2.6.6) I proposed a patch to update MAINTAINERS, but
Jeff said he wanted to wait some time. I don't know if such change is
now possible/wanted.
AFAIK Ollie's email address bounces.
--
Daniele Venzano
http://www.brownhat.org
next prev parent reply other threads:[~2005-03-11 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 20:17 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 [this message]
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=c37a8fd17af92b648c6474904e0003c0@libero.it \
--to=webvenza@libero.it \
--cc=chrisw@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®