From: Chris Wright <chrisw@osdl.org>
To: Daniele Venzano <webvenza@libero.it>
Cc: Chris Wright <chrisw@osdl.org>,
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 11:36:06 -0800 [thread overview]
Message-ID: <20050311193606.GL5389@shell0.pdx.osdl.net> (raw)
In-Reply-To: <c37a8fd17af92b648c6474904e0003c0@libero.it>
* Daniele Venzano (webvenza@libero.it) wrote:
>
> I have been acting maintainer for more than a year now, and I'm
> completely fine with the patch.
Thanks.
-chris
next prev parent reply other threads:[~2005-03-11 19: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 [this message]
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=20050311193606.GL5389@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=stable@kernel.org \
--cc=webvenza@libero.it \
/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).