From: "David S. Miller" <davem@redhat.com>
To: srompf@isg.de
Cc: thockin@sun.com, netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: PATCH idea - netlink and link changes
Date: Sat, 12 Oct 2002 02:11:09 -0700 (PDT) [thread overview]
Message-ID: <20021012.021109.26965691.davem@redhat.com> (raw)
In-Reply-To: <3DA7EA1B.3D0430F@isg.de>
From: Stefan Rompf <srompf@isg.de>
Date: Sat, 12 Oct 2002 11:23:39 +0200
IMHO we should merge the patches, taking your one workqueue per device
approach and my usage of IFF_RUNNING as a mirror bit. What do other
netdev people think?
I'm waiting for Jamal to catch up on his email and comment
on this stuff, he had very clear ideas about what should
be happening here.
next prev parent reply other threads:[~2002-10-12 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 16:59 PATCH idea - netlink and link changes Tim Hockin
2002-10-12 0:12 ` Stefan Rompf
2002-10-12 9:23 ` Stefan Rompf
2002-10-12 9:11 ` David S. Miller [this message]
2002-10-12 13:10 ` jamal
2002-10-14 18:07 ` Tim Hockin
2002-10-14 18:17 ` Stefan Rompf
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=20021012.021109.26965691.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=srompf@isg.de \
--cc=thockin@sun.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).