From: Ulrich Drepper <drepper@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inconsistency between SIOCGIFCONF and SIOCGIFNAME
Date: Wed, 30 Jun 2004 00:51:31 -0700 [thread overview]
Message-ID: <40E27103.8040304@redhat.com> (raw)
In-Reply-To: <20040629221341.52824096.davem@redhat.com>
David S. Miller wrote:
> This is especially unnecessary since rtnetlink does exactly what you
> want already, so we don't need to add a new interface nor change the
> semantics of an old one.
I do have code using netlink in cvs now. We'll see whether people complain.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2004-06-30 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 4:06 inconsistency between SIOCGIFCONF and SIOCGIFNAME Ulrich Drepper
2004-06-29 8:26 ` David S. Miller
2004-06-29 16:22 ` Ulrich Drepper
2004-06-29 19:09 ` Ulrich Drepper
2004-06-29 21:19 ` David S. Miller
2004-06-30 4:45 ` Ulrich Drepper
2004-06-30 5:10 ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-30 5:13 ` David S. Miller
2004-06-30 7:51 ` Ulrich Drepper [this message]
2004-06-30 19:59 ` David S. Miller
2004-06-29 16:32 ` Stephen Hemminger
2004-06-29 19:11 ` Ulrich Drepper
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=40E27103.8040304@redhat.com \
--to=drepper@redhat.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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.