From: Jiri Skala <jskala@redhat.com>
To: netdev@vger.kernel.org
Subject: iputils flowlabel
Date: Wed, 28 Apr 2010 10:51:48 +0200 [thread overview]
Message-ID: <1272444708.3035.39.camel@localhost.localdomain> (raw)
Hi,
I'd like to ask about current state of FLOWLABEL functionality. This is
currently wrapped into define and disabled by default.
Trying to enable it means to define (somehow = in proprietary header)
in6_flowlabel_req structure because usage of linux/in6.h conflicts with
glibc's headers.
Is flowlabel fnc inside ifdef due to described 'header' issue? Any other
comment to this topic?
Thanks
Jiri
next reply other threads:[~2010-04-28 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 8:51 Jiri Skala [this message]
2010-06-17 2:20 ` iputils flowlabel 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=1272444708.3035.39.camel@localhost.localdomain \
--to=jskala@redhat.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