public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] iflib(9): Add support for cloning pseudo interfaces
Date: Fri, 24 Aug 2018 13:11:00 -0000	[thread overview]
Message-ID: <20180824131136.72094.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=44e0190a8c060a4fa95c25b4ed675e048e125f55

commit 44e0190a8c060a4fa95c25b4ed675e048e125f55
Author: mmacy <mmacy@FreeBSD.org>
Date:   Fri May 11 20:08:28 2018 +0000

    iflib(9): Add support for cloning pseudo interfaces
    
    Part 3 of many ...
    The VPC framework relies heavily on cloning pseudo interfaces
    (vmnics, vpc switch, vcpswitch port, hostif, vxlan if, etc).
    
    This pulls in that piece. Some ancillary changes get pulled
    in as a side effect.
    
    Reviewed by:	shurd@
    Approved by:	sbruno@
    Sponsored by:	Joyent, Inc.
    Differential Revision:	https://reviews.freebsd.org/D15347

Diff:
---
 newlib/libc/sys/rtems/include/net/if.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/newlib/libc/sys/rtems/include/net/if.h b/newlib/libc/sys/rtems/include/net/if.h
index 83a4328..0cd082f 100644
--- a/newlib/libc/sys/rtems/include/net/if.h
+++ b/newlib/libc/sys/rtems/include/net/if.h
@@ -162,6 +162,9 @@ struct if_data {
 #define	IFF_STATICARP	0x80000		/* (n) static ARP */
 #define	IFF_DYING	0x200000	/* (n) interface is winding down */
 #define	IFF_RENAMING	0x400000	/* (n) interface is being renamed */
+#define	IFF_NOGROUP	0x800000	/* (n) interface is not part of any groups */
+
+
 /*
  * Old names for driver flags so that user space tools can continue to use
  * the old (portable) names.


                 reply	other threads:[~2018-08-24 13:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180824131136.72094.qmail@sourceware.org \
    --to=sh@sourceware.org \
    --cc=newlib-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).