All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Rompf <srompf@isg.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: Patch resubmission: RFC2863 operstatus for 2.5.50
Date: Wed, 04 Dec 2002 10:44:58 +0100	[thread overview]
Message-ID: <3DEDCE9A.61FDEBBC@isg.de> (raw)
In-Reply-To: 3DED51E9.1080408@pobox.com

Hi,

Jeff Garzik wrote:

> Pardon my dumb question, but what parts of RFC2863 require kernel
> additions over and above your link state patch?

the kernel does not know LOWERLAYERDOWN, TESTING, DORMANT, UNKNOWN. They
can be useful when drivers adopt to this scheme.

> Your second patch I am less enthusiastic about than the first... :(

Well, with your opinion I count two against two: I want it, Jamal has
proposed the semantics, and Alexey doesn't want to waste a single bit of
a netlink message for this.

What now?

Stefan

  reply	other threads:[~2002-12-04  9:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  9:22 Patch resubmission: RFC2863 operstatus for 2.5.49 Stefan Rompf
2002-11-26 10:15 ` David S. Miller
2002-11-26 15:36   ` Stefan Rompf
2002-12-03 22:22   ` Patch resubmission: RFC2863 operstatus for 2.5.50 Stefan Rompf
2002-12-04  0:52     ` Jeff Garzik
2002-12-04  9:44       ` Stefan Rompf [this message]
2002-12-04 18:15         ` Jeff Garzik
2002-12-04 13:11       ` jamal
2002-12-04 17:42         ` Jeff Garzik
2002-12-09 13:27           ` jamal
2002-12-09 23:10             ` Stefan Rompf
2002-12-10  3:55             ` Jeff Garzik
2002-12-12 13:21               ` jamal
2002-12-04 19:39     ` David S. Miller
2002-11-29 12:56 ` Patch resubmission: RFC2863 operstatus for 2.5.49 jamal
2002-12-03 23:04   ` Stefan Rompf
2002-12-04 13:06     ` jamal

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=3DEDCE9A.61FDEBBC@isg.de \
    --to=srompf@isg.de \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.