From: Will Wagner <will_wagner@carallon.com>
To: eCos development list <ecos-devel@sourceware.org>
Subject: [RFC 8/9] * Fix LWIP compiler warnings
Date: Thu, 27 Jun 2013 19:22:00 -0000 [thread overview]
Message-ID: <51CC910A.9070901@carallon.com> (raw)
Add some casts to prevent compiler warnings
Signed-off-by: Andrew Parlane <andrewp@carallon.com>
Signed-off-by: Will Wagner <willw@carallon.com>
---
packages/net/lwip_tcpip/current/include/lwip/pbuf.h | 2 +-
packages/net/lwip_tcpip/current/src/core/ipv4/igmp.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/packages/net/lwip_tcpip/current/include/lwip/pbuf.h
b/packages/net/lwip_tcpip/current/include/lwip/pbuf.h
index 99d5443..99cf20a 100644
--- a/packages/net/lwip_tcpip/current/include/lwip/pbuf.h
+++ b/packages/net/lwip_tcpip/current/include/lwip/pbuf.h
@@ -129,7 +129,7 @@ struct pbuf_custom {
#endif /* PBUF_POOL_FREE_OOSEQ */
#if NO_SYS && PBUF_POOL_FREE_OOSEQ
extern volatile u8_t pbuf_free_ooseq_pending;
-void pbuf_free_ooseq();
+void pbuf_free_ooseq(void);
/** When not using sys_check_timeouts(), call PBUF_CHECK_FREE_OOSEQ()
at regular intervals from main level to check if ooseq pbufs need
to be
freed! */
diff --git a/packages/net/lwip_tcpip/current/src/core/ipv4/igmp.c
b/packages/net/lwip_tcpip/current/src/core/ipv4/igmp.c
index 45bb5d9..f273b2f 100644
--- a/packages/net/lwip_tcpip/current/src/core/ipv4/igmp.c
+++ b/packages/net/lwip_tcpip/current/src/core/ipv4/igmp.c
@@ -166,8 +166,8 @@ igmp_init(void)
* Dump global IGMP groups list
*/
void
-igmp_dump_group_list()
-{
+igmp_dump_group_list(void)
+{
struct igmp_group *group = igmp_group_list;
while (group != NULL) {
--
1.8.1.msysgit.1
reply other threads:[~2013-06-27 19:22 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=51CC910A.9070901@carallon.com \
--to=will_wagner@carallon.com \
--cc=ecos-devel@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).