netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Val Henson <val.henson@gmail.com>,
	Grant Grundler <grundler@parisc-linux.org>,
	Andrew Morton <akpm@osdl.org>
Cc: Netdev List <netdev@vger.kernel.org>
Subject: New tulip maintainer...
Date: Thu, 08 Jun 2006 11:41:28 -0400	[thread overview]
Message-ID: <44884528.2040804@garzik.org> (raw)

Now that we have a new tulip maintainer, perhaps a resend of the 
long-outstanding tulip phy patches could be resent?

With an active tulip maintainer, the "too-long mdelay" would hopefully 
only exist temporarily -- with the proper fix being to move that code 
into a kernel thread (workqueue?) long term.

	Jeff



             reply	other threads:[~2006-06-08 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 15:41 Jeff Garzik [this message]
2006-06-08 16:06 ` New tulip maintainer Grant Grundler
2006-06-08 21:24   ` Valerie Henson

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=44884528.2040804@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=grundler@parisc-linux.org \
    --cc=netdev@vger.kernel.org \
    --cc=val.henson@gmail.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).