From: "David S. Miller" <davem@davemloft.net>
To: dacker@roinet.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: expose vlan structure to user space
Date: Fri, 14 Apr 2006 13:55:56 -0700 (PDT) [thread overview]
Message-ID: <20060414.135556.91849056.davem@davemloft.net> (raw)
In-Reply-To: <443FA08A.8040900@roinet.com>
From: David Acker <dacker@roinet.com>
Date: Fri, 14 Apr 2006 09:15:54 -0400
> David S. Miller wrote:
> > I think this really belongs in a portable header file
> > in glibc somewhere.
>
> David, while I can try to work with the glibc folks, I don't understand
> how this patch would be different from what if_ether.h exposes to user
> space today. Why is one appropriate and the other not? I am not trying
> to be a pain; I am just trying to understand the rationale so that I can
> explain it to others.
Doing stupid things in the past does not equate to being a reason
to keep doing so in the future.
next prev parent reply other threads:[~2006-04-14 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4436BB69.3010205@roinet.com>
2006-04-14 13:15 ` [PATCH] net: expose vlan structure to user space David Acker
2006-04-14 20:55 ` David S. Miller [this message]
2006-04-14 21:10 ` David Acker
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=20060414.135556.91849056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dacker@roinet.com \
--cc=netdev@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 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).