From: "David S. Miller" <davem@davemloft.net>
To: Matt Mackall <mpm@selenic.com>
Cc: romieu@fr.zoreil.com, alexn@dsv.su.se, jgarzik@pobox.com,
netdev@oss.sgi.com
Subject: Re: Reproducible panics with tulip
Date: Fri, 18 Mar 2005 19:47:51 -0800 [thread overview]
Message-ID: <20050318194751.3fade099.davem@davemloft.net> (raw)
In-Reply-To: <20050319031321.GA25554@waste.org>
On Fri, 18 Mar 2005 19:13:21 -
Matt Mackall <mpm@selenic.com> wrote:
> Please, cc: me on such things. I sent this fix a while back, but DaveM
> never acked it.
It's in my backlog, never fear :-)
next prev parent reply other threads:[~2005-03-19 3:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 20:36 Reproducible panics with tulip Alexander Nyberg
2005-03-18 21:52 ` Francois Romieu
2005-03-18 22:39 ` Francois Romieu
2005-03-19 3:13 ` Matt Mackall
2005-03-19 3:47 ` David S. Miller [this message]
2005-03-19 11:29 ` Alexander Nyberg
2005-03-19 9:21 ` Alexander Nyberg
2005-03-19 10:20 ` Francois Romieu
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=20050318194751.3fade099.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexn@dsv.su.se \
--cc=jgarzik@pobox.com \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
/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).