[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #50816] netif_add() prototype depends on configuration
From: |
Daniel Elstner |
Subject: |
[lwip-devel] [bug #50816] netif_add() prototype depends on configuration |
Date: |
Sun, 16 Apr 2017 18:24:35 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/57.0.2987.98 Chrome/57.0.2987.98 Safari/537.36 |
URL:
<http://savannah.nongnu.org/bugs/?50816>
Summary: netif_add() prototype depends on configuration
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: danielk
Submitted on: Mon 17 Apr 2017 12:24:34 AM CEST
Category: None
Severity: 3 - Normal
Item Group: Feature Request
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
lwIP version: git head
_______________________________________________________
Details:
Currently I need to do this in my code:
struct netif *netif = netif_add(ðernet_netif,
#if LWIP_IPV4
NULL, NULL, NULL,
#endif
NULL, ðernetif_init, &tcpip_input);
I think that's unnecessarily ugly. How about the following addition to the
netif API to avoid this?
#if LWIP_IPV4
# define netif_add_no_addr(netif, state, init, input) \
netif_add(netif, NULL, NULL, NULL, state, init, input)
#else
# define netif_add_no_addr(netif, state, init, input) \
netif_add(netif, state, init, input)
#endif /* !LWIP_IPV4 */
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?50816>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #50816] netif_add() prototype depends on configuration,
Daniel Elstner <=