From: Stefan Rompf <srompf@isg.de>
To: kuznet@ms2.inr.ac.ru, jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com
Subject: Re: Patch: Idea for RFC2863 conform OperStatus
Date: Mon, 14 Oct 2002 14:42:22 +0200 [thread overview]
Message-ID: <3DAABBAE.79E22EB6@isg.de> (raw)
In-Reply-To: 200210132204.CAA09385@sex.inr.ac.ru
Alexey, Jamal,
the first version of this patch just added the feature to distribute
state changes created by netif_carrier_on()/_off() inside the kernel and
to netlink via netdev_state_change(). This is still the part most
important to me - not only in 2.5, but also as a 2.4 backport.
I don't think RFC2863 state keeping makes much sense if we cannot
forward the results to userspace. So if you are happy with keeping the
current semantics, but using the more sophisticated implementation of
forwarding worked out last weekend, I'll be happy to provide a new patch
(also adressing Jamal's nitpicks). Just agree on one way.
Cheers, Stefan
next prev parent reply other threads:[~2002-10-14 12:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 13:23 Patch: Idea for RFC2863 conform OperStatus Stefan Rompf
2002-10-12 13:13 ` jamal
2002-10-13 12:48 ` Stefan Rompf
2002-10-13 14:04 ` jamal
2002-10-15 9:53 ` Stefan Rompf
2002-10-16 2:49 ` jamal
2002-10-21 21:38 ` Stefan Rompf
2002-10-12 14:09 ` jamal
2002-10-13 19:14 ` kuznet
2002-10-13 20:30 ` jamal
2002-10-13 21:00 ` kuznet
2002-10-13 21:34 ` jamal
2002-10-13 22:04 ` kuznet
2002-10-14 12:42 ` Stefan Rompf [this message]
2002-10-14 13:11 ` jamal
2002-10-14 13:38 ` jamal
2002-10-14 18:14 ` Stefan Rompf
2002-10-14 18:55 ` David Brownell
2002-10-14 19:03 ` David Brownell
2002-10-14 13:01 ` jamal
2002-10-14 10:38 ` bert hubert
2002-10-14 11:16 ` Robert Olsson
2002-10-14 11:11 ` bert hubert
2002-10-14 11:50 ` Robert Olsson
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=3DAABBAE.79E22EB6@isg.de \
--to=srompf@isg.de \
--cc=hadi@cyberus.ca \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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).