From: "David S. Miller" <davem@redhat.com>
To: "YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: xma@us.ibm.com, mashirle@us.ibm.com, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] IPv6 MIB:ipv6DefaultRouterTable
Date: Thu, 15 Jan 2004 11:37:00 -0800 [thread overview]
Message-ID: <20040115113700.166ddfb0.davem@redhat.com> (raw)
In-Reply-To: <20040116.041950.35757995.yoshfuji@linux-ipv6.org>
On Fri, 16 Jan 2004 04:19:50 +0900 (JST)
YOSHIFUJI Hideaki / _$B5HF#1QL@ <yoshfuji@linux-ipv6.org> wrote:
> In article <OFC6D64AE0.CEE7DA5F-ON87256E1C.0068A56A@us.ibm.com> (at Thu, 15 Jan 2004 11:09:47 -0800), Shirley Ma <xma@us.ibm.com> says:
>
> > But if no applications use this value, and nothing is boken. It's not
> > harmful to change the kernel to provide MIBs in as-is format.
>
> Shirley, nobody can prove that nothing will be broken. :-)
And also, the current situation is OK as long as this value we present now
can be converted into the desired value. Is this the case?
next prev parent reply other threads:[~2004-01-15 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 19:09 [PATCH] IPv6 MIB:ipv6DefaultRouterTable Shirley Ma
2004-01-15 19:19 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:37 ` David S. Miller [this message]
2004-01-15 19:47 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 19:59 Shirley Ma
2004-01-15 19:30 Shirley Ma
2004-01-15 19:36 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:38 ` David S. Miller
2004-01-15 19:53 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 19:45 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 18:26 Shirley Ma
2004-01-15 18:36 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-20 0:21 IPv6 MIB:ipv6PrefixTable implementation Shirley Ma
2003-12-05 21:51 ` [PATCH] IPv6 MIB:ipv6Prefix netlink notification Shirley Ma
2003-12-05 22:57 ` David S. Miller
2004-01-15 0:22 ` [PATCH] IPv6 MIB:ipv6DefaultRouterTable Shirley Ma
2004-01-15 9:03 ` YOSHIFUJI Hideaki / 吉藤英明
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=20040115113700.166ddfb0.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mashirle@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=xma@us.ibm.com \
--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 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.