Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Fred.L.Templin@boeing.com
Cc: yoshfuji@linux-ipv6.org, shemminger@linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 04/05] ipv6: RFC4214 Support
Date: Thu, 08 Nov 2007 15:30:21 -0800 (PST)	[thread overview]
Message-ID: <20071108.153021.258449702.davem@davemloft.net> (raw)
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029EDC09@XCH-NW-7V2.nw.nos.boeing.com>

From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Date: Thu, 8 Nov 2007 13:01:34 -0800

> > Hmm, what is missing from API POV?
> 
> This would have to be determined under a follow-on project (hopefully
> with input from others) after we have gained operational experience.

I personally don't buy any of this desire to avoid iproute2
changes at this time.

This is never how we handle this kind of situation.

We add in the new feature, and add support to iproute2 in
parallel.  If we screw it up we figure that out quickly
and fix things before it's been deployed for too long.

I suspect you simply want users to just be able to use the
new feature with only a kernel patch, but that's not an
appropriate reason to not do things correctly when submitting
a feature upstream.

Please use the new name in the kernel side changes and implement
iproute2 support for these ISATAP devices.

Thank you.


  reply	other threads:[~2007-11-09  1:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07  1:16 [PATCH 04/05] ipv6: RFC4214 Support Templin, Fred L
2007-11-07 16:16 ` Templin, Fred L
2007-11-07 18:36 ` YOSHIFUJI Hideaki / 吉藤英明
2007-11-07 18:41   ` Templin, Fred L
2007-11-07 18:45     ` Stephen Hemminger
2007-11-07 19:12       ` Templin, Fred L
2007-11-08 14:26         ` YOSHIFUJI Hideaki / 吉藤英明
2007-11-08 21:01           ` Templin, Fred L
2007-11-08 23:30             ` David Miller [this message]
2007-11-10 20:56 ` Andi Kleen

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=20071108.153021.258449702.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Fred.L.Templin@boeing.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=yoshfuji@linux-ipv6.org \
    /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